From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Yuho Choi <dbgh9129@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Brian Masney <bmasney@redhat.com>, Kees Cook <kees@kernel.org>,
"Rafael J. Wysocki (Intel)" <rafael@kernel.org>,
Thierry Reding <treding@nvidia.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: at91: keep securam node alive while mapping it
Date: Tue, 2 Jun 2026 09:51:20 +0300 [thread overview]
Message-ID: <17775f6d-3f72-4a05-865a-897d76f6feb3@tuxon.dev> (raw)
In-Reply-To: <20260529042051.1626978-1-dbgh9129@gmail.com>
On 5/29/26 07:20, Yuho Choi wrote:
> pmc_register_ops() gets an owned reference to the
> "atmel,sama5d2-securam" node with of_find_compatible_node(). The
> success path dropped that reference before passing the node to
> of_iomap(), leaving of_iomap() to consume a node pointer after the caller
> had released its reference.
>
> Move of_node_put() after of_iomap() so the node remains referenced for
> the mapping operation. The unavailable-node error path already releases
> the reference.
>
> Fixes: 4d21be864092 ("clk: at91: pmc: execute suspend/resume only for backup mode")
> Signed-off-by: Yuho Choi<dbgh9129@gmail.com>
Missed to mention, applied to clk-microchip-fixes, thanks!
prev parent reply other threads:[~2026-06-02 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 4:20 Yuho Choi
2026-05-29 21:02 ` Alexandre Belloni
2026-06-01 15:20 ` Brian Masney
2026-06-02 6:51 ` Claudiu Beznea [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=17775f6d-3f72-4a05-865a-897d76f6feb3@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=bmasney@redhat.com \
--cc=dbgh9129@gmail.com \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®