From: Markus Elfring <Markus.Elfring@web.de>
To: vulab@iscas.ac.cn, linux-arm-kernel@lists.infradead.org,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc: ti: pruss: fix double free in pruss_clk_mux_setup()
Date: Sun, 28 Dec 2025 13:55:07 +0100 [thread overview]
Message-ID: <8570d445-30d9-4742-afc6-5484cb7d3d75@web.de> (raw)
In-Reply-To: <20251225143256.2363630-1-vulab@iscas.ac.cn>
…
> Fix by using a separate label to avoid the duplicate of_node_put().
May you return directly?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v6.19-rc2#n532
Regards,
Markus
next prev parent reply other threads:[~2025-12-28 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 14:32 [PATCH] soc: ti: pruss: fix double free in pruss_clk_mux_setup() Wentao Liang
2025-12-28 12:55 ` Markus Elfring [this message]
2026-01-05 13:42 ` Nishanth Menon
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=8570d445-30d9-4742-afc6-5484cb7d3d75@web.de \
--to=markus.elfring@web.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vulab@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