From: Markus Elfring <Markus.Elfring@web.de>
To: Lu Yao <yaolu@kylinos.cn>,
dri-devel@lists.freedesktop.org,
Jianmin Lv <lvjianmin@loongson.cn>,
Qianhai Wu <wuqianhai@loongson.cn>
Cc: LKML <linux-kernel@vger.kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Icenowy Zheng <zhengxingda@iscas.ac.cn>,
Mingcong Bai <jeffbai@aosc.io>, Xi Ruoyao <xry111@xry111.site>
Subject: Re: [PATH] drm/loongson: fix pci_dev refcount leak in lsdc_get_dedicated_vram
Date: Tue, 19 May 2026 10:00:11 +0200 [thread overview]
Message-ID: <8ba844ab-9851-4045-a4e8-a96e6d1511e2@web.de> (raw)
In-Reply-To: <20260519073807.142372-1-yaolu@kylinos.cn>
> Need call 'pci_dev_put' after 'pci_get_domain_bus_and_slot'.
See also once more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.1-rc4#n94
* How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
* Would it be helpful to append parentheses to function names?
https://elixir.bootlin.com/linux/v7.1-rc3/source/drivers/gpu/drm/loongson/lsdc_drv.c#L154-L190
Regards,
Markus
next prev parent reply other threads:[~2026-05-19 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:38 [PATH] drm/loongson: fix pci_dev refcount leak in lsdc_get_dedicated_vram yaolu
2026-05-19 8:00 ` Markus Elfring [this message]
2026-05-20 1:47 ` [PATCH v2] drm/loongson: fix pci_dev refcount leak in lsdc_get_dedicated_vram() yaolu
2026-05-20 9:05 ` Markus Elfring
2026-05-20 9:11 ` Xi Ruoyao
2026-05-20 12:05 ` [PATCH v3] drm/loongson: rm unused member lsdc_device->gpu yaolu
2026-05-20 13:19 ` Markus Elfring
2026-05-25 11:54 ` Claude review: drm/loongson: fix pci_dev refcount leak in lsdc_get_dedicated_vram() Claude Code Review Bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ba844ab-9851-4045-a4e8-a96e6d1511e2@web.de \
--to=markus.elfring@web.de \
--cc=chenhuacai@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeffbai@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=wuqianhai@loongson.cn \
--cc=xry111@xry111.site \
--cc=yaolu@kylinos.cn \
--cc=zhengxingda@iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox