From: Stephen Boyd <sboyd@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>,
Marco Pagani <marpagan@redhat.com>,
Michael Turquette <mturquette@baylibre.com>
Cc: Marco Pagani <marpagan@redhat.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] clk: socfpga: arria10: use of_clk_add_hw_provider and improve error handling
Date: Tue, 21 Mar 2023 16:53:54 -0700 [thread overview]
Message-ID: <3d2a4063dfa82d49dd98ee8f615f3aec.sboyd@kernel.org> (raw)
In-Reply-To: <20221209152913.1335068-7-marpagan@redhat.com>
Quoting Marco Pagani (2022-12-09 07:29:13)
> The function of_clk_add_provider() has been deprecated, so use its
> suggested replacement of_clk_add_hw_provider() instead.
>
> Since of_clk_add_hw_provider() can fail, like of_clk_add_provider(),
> check its return value and do the error handling.
>
> The return type of the init function has been changed to void since
> the return value was not used, and the indentation of the parameters has
> been aligned to match open parenthesis, as suggested by checkpatch.
>
> Signed-off-by: Marco Pagani <marpagan@redhat.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2023-03-21 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 15:29 [PATCH 0/6] clk: socfpga: use of_clk_add_hw_provider and improve error handling Marco Pagani
2022-12-09 15:29 ` [PATCH 1/6] " Marco Pagani
2023-03-21 23:53 ` Stephen Boyd
2022-12-09 15:29 ` [PATCH 2/6] clk: socfpga: arria10: " Marco Pagani
2023-03-21 23:53 ` Stephen Boyd
2022-12-09 15:29 ` [PATCH 3/6] clk: socfpga: " Marco Pagani
2023-03-21 23:53 ` Stephen Boyd
2022-12-09 15:29 ` [PATCH 4/6] clk: socfpga: arria10: " Marco Pagani
2023-03-21 23:53 ` Stephen Boyd
2022-12-09 15:29 ` [PATCH 5/6] clk: socfpga: " Marco Pagani
2023-03-21 23:53 ` Stephen Boyd
2022-12-09 15:29 ` [PATCH 6/6] clk: socfpga: arria10: " Marco Pagani
2023-03-21 23:53 ` Stephen Boyd [this message]
2023-03-21 23:47 ` [PATCH 0/6] clk: socfpga: " Stephen Boyd
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=3d2a4063dfa82d49dd98ee8f615f3aec.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marpagan@redhat.com \
--cc=mturquette@baylibre.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