From: Markus Elfring <Markus.Elfring@web.de>
To: Manush Prajwal <manushprajwal555@gmail.com>,
imx@lists.linux.dev, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Frank Li <Frank.Li@nxp.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>, Jacky Bai <ping.bai@nxp.com>,
Linus Walleij <linusw@kernel.org>,
Md Rabbani <rabbanyhmm@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v2] pinctrl: imx1-core: fix device_node refcount leak
Date: Mon, 24 Aug 2026 09:35:32 +0200 [thread overview]
Message-ID: <f42f463a-e2cb-486d-91af-40c646d38b6b@web.de> (raw)
In-Reply-To: <20260814190527.969-1-manushprajwal555@gmail.com>
…
> Rework both loops around for_each_child_of_node_scoped() instead of
> adding manual of_node_put() calls, matching the sibling helper in
> pinctrl-imx.c and imx1_pinctrl_parse_dt() in this same file, which
> already use the scoped variant.
How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
See also:
* https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.2#n145
* https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.2#n34
Regards,
Markus
prev parent reply other threads:[~2026-08-24 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 19:05 [PATCH v2] pinctrl: imx1-core: fix device_node refcount leak manushprajwal
2026-08-14 20:50 ` Frank Li
2026-08-24 7:35 ` Markus Elfring [this message]
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=f42f463a-e2cb-486d-91af-40c646d38b6b@web.de \
--to=markus.elfring@web.de \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manushprajwal555@gmail.com \
--cc=ping.bai@nxp.com \
--cc=rabbanyhmm@gmail.com \
--cc=s.hauer@pengutronix.de \
/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