From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] clk: Print an error when clk registration fails
Date: Tue, 04 Mar 2025 13:55:10 -0800 [thread overview]
Message-ID: <2f6d1043d90ab901e6d0dfc09dcff358.sboyd@kernel.org> (raw)
In-Reply-To: <20250226235408.1339266-1-sboyd@kernel.org>
Quoting Stephen Boyd (2025-02-26 15:54:07)
> We have a lot of driver code that prints an error message when
> registering a clk fails. Do that in the core function instead to
> consolidate code. This also helps drivers avoid the anti-pattern of
> accessing the struct clk_hw::init pointer after registration.
>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
Applied to clk-next
prev parent reply other threads:[~2025-03-04 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 23:54 [PATCH] clk: Print an error when clk registration fails Stephen Boyd
2025-03-04 21:55 ` Stephen Boyd [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=2f6d1043d90ab901e6d0dfc09dcff358.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
/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