From: Markus Elfring <Markus.Elfring@web.de>
To: Siyang Liu <1972843537@qq.com>, sparclinux@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andreas Larsson <andreas@gaisler.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2] arch: fix resource leak in jbusmc_probe()
Date: Mon, 21 Jul 2025 09:18:14 +0200 [thread overview]
Message-ID: <45b8941a-b6bf-4b48-ad1b-cc6ba46b8642@web.de> (raw)
In-Reply-To: <tencent_60B856B729FE434916EF57CDF5286D69A008@qq.com>
…> This can lead to leakage of device node reference counts,
> which may result in kernel resources not being released.
…
See also one more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16-rc6#n94
* Will you become more interested in additional tags (like “Fixes” and “Cc”)?
* Would the subsystem specification “sparc” be more appropriate
in the summary phrase?
…> ---
> arch/sparc/kernel/chmc.c | 10 +++++++---
…
How do you think about to improve your version management?
https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16-rc6#n784
Regards,
Markus
next prev parent reply other threads:[~2025-07-21 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 9:22 [PATCH] arch: fix resource leak in chmc.c Jacky Liu
2025-07-18 13:25 ` Krzysztof Kozlowski
2025-07-21 2:04 ` jackysliu
2025-07-18 13:43 ` [PATCH] " Markus Elfring
2025-07-21 3:57 ` [PATCH v2] arch: fix resource leak in jbusmc_probe() jackysliu
2025-07-21 7:18 ` Markus Elfring [this message]
2025-07-21 7:55 ` [PATCH v3] sparc: " jackysliu
2025-07-21 8:17 ` Markus Elfring
2025-07-22 6:22 ` Krzysztof Kozlowski
2025-07-21 8:25 ` [PATCH v2] arch: " Krzysztof Kozlowski
2025-07-21 3:49 [PATCH] dm-raid: do not include dm-core.h Pavel Tikhomirov
2025-07-21 3:56 ` [PATCH v2] arch: fix resource leak in jbusmc_probe() jackysliu
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=45b8941a-b6bf-4b48-ad1b-cc6ba46b8642@web.de \
--to=markus.elfring@web.de \
--cc=1972843537@qq.com \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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
all inboxes | Powered by JetHome®