From: Robin Murphy <robin.murphy@arm.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Manush Prajwal <manushprajwal555@gmail.com>
Subject: Re: [PATCH] bus: arm-cci: fix device_node refcount leak in cci_probe_ports()
Date: Mon, 24 Aug 2026 12:48:55 +0100 [thread overview]
Message-ID: <566ce354-88f0-4e68-86a4-a8d68bb65254@arm.com> (raw)
In-Reply-To: <5bd32eba-881a-4395-841d-909536262dcb@web.de>
On 2026-08-24 8:00 am, Markus Elfring wrote:
>> cci_probe_ports() has two device_node refcount bugs in its
>> for_each_available_child_of_node() loop over "cp":
> …
>
> How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
No.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.2-rc5#n15
>
> See also:
> * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.2-rc5#n145
> * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.2-rc5#n34
>
> Regards,
> Markus
next prev parent reply other threads:[~2026-08-24 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 15:57 [PATCH] bus: arm-cci: fix device_node refcount leak in cci_probe_ports() Manush Prajwal
2026-08-24 7:00 ` Markus Elfring
2026-08-24 11:48 ` Robin Murphy [this message]
2026-08-24 12:00 ` Markus Elfring
2026-08-24 11:41 ` Robin Murphy
-- strict thread matches above, loose matches on Subject: below --
2026-08-13 11:10 Manush Prajwal
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=566ce354-88f0-4e68-86a4-a8d68bb65254@arm.com \
--to=robin.murphy@arm.com \
--cc=Markus.Elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manushprajwal555@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).