public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Lu Yao <yaolu@kylinos.cn>, dri-devel@lists.freedesktop.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	Icenowy Zheng <zhengxingda@iscas.ac.cn>,
	Jianmin Lv <lvjianmin@loongson.cn>,
	Mingcong Bai <jeffbai@aosc.io>,
	Qianhai Wu <wuqianhai@loongson.cn>,
	Xi Ruoyao <xry111@xry111.site>
Subject: Re: [PATCH v2] drm/loongson: fix pci_dev refcount leak in lsdc_get_dedicated_vram()
Date: Wed, 20 May 2026 11:05:16 +0200	[thread overview]
Message-ID: <6ccfe40e-fe4b-4a05-9ab1-82cdfcaa0811@web.de> (raw)
In-Reply-To: <20260520014721.32696-1-yaolu@kylinos.cn>

> Need to call pci_dev_put() after pci_get_domain_bus_and_slot().

Can development interests occasionally grow also for further patch requirements?

* Usage of imperative mood

* Reference counting

* Completion of exception handling

* Related tags
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.1-rc4#n34


Regards,
Markus

  reply	other threads:[~2026-05-20  9:06 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
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 [this message]
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=6ccfe40e-fe4b-4a05-9ab1-82cdfcaa0811@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