From: Stephen Boyd <sboyd@kernel.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linux-clk@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Andreas Färber" <afaerber@suse.de>,
"Saravanan Sekar" <sravanhome@gmail.com>,
"Parthiban Nallathambi" <pn@denx.de>,
linux-actions@lists.infradead.org
Subject: Re: [PATCH v4 1/5] clk: actions: Terminate clk_div_table with sentinel element
Date: Fri, 11 Mar 2022 18:16:30 -0800 [thread overview]
Message-ID: <20220312021632.97A49C340E9@smtp.kernel.org> (raw)
In-Reply-To: <20220218000922.134857-2-j.neuschaefer@gmx.net>
Quoting Jonathan Neuschäfer (2022-02-17 16:09:17)
> In order that the end of a clk_div_table can be detected, it must be
> terminated with a sentinel element (.div = 0).
>
> In owl-s900.s, the { 0, 8 } element was probably meant to be just that,
> so this patch changes { 0, 8 } to { 0, 0 }.
>
> Fixes: d47317ca4ade1 ("clk: actions: Add S700 SoC clock support")
> Fixes: d85d20053e195 ("clk: actions: Add S900 SoC clock support")
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2022-03-12 2:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 0:09 [PATCH v4 0/5] clk drivers: Terminate clk_div_table with sentinel element Jonathan Neuschäfer
2022-02-18 0:09 ` [PATCH v4 1/5] clk: actions: " Jonathan Neuschäfer
2022-03-12 2:16 ` Stephen Boyd [this message]
2022-02-18 0:09 ` [PATCH v4 2/5] clk: loongson1: " Jonathan Neuschäfer
2022-03-12 2:16 ` Stephen Boyd
2022-02-18 0:09 ` [PATCH v4 3/5] clk: hisilicon: " Jonathan Neuschäfer
2022-03-12 2:16 ` Stephen Boyd
2022-02-18 0:09 ` [PATCH v4 4/5] clk: clps711x: " Jonathan Neuschäfer
2022-03-12 2:16 ` Stephen Boyd
2022-02-18 0:09 ` [PATCH v4 5/5] clk: actions: Make sentinel elements more obvious Jonathan Neuschäfer
2022-03-12 2:17 ` 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=20220312021632.97A49C340E9@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=afaerber@suse.de \
--cc=f4bug@amsat.org \
--cc=j.neuschaefer@gmx.net \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mturquette@baylibre.com \
--cc=pn@denx.de \
--cc=sravanhome@gmail.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;
as well as URLs for NNTP newsgroup(s).