From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: 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>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Alexander Shiyan" <shc_work@mail.ru>,
"Mike Turquette" <mturquette@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>
Subject: [PATCH v4 4/5] clk: clps711x: Terminate clk_div_table with sentinel element
Date: Fri, 18 Feb 2022 01:09:20 +0100 [thread overview]
Message-ID: <20220218000922.134857-5-j.neuschaefer@gmx.net> (raw)
In-Reply-To: <20220218000922.134857-1-j.neuschaefer@gmx.net>
In order that the end of a clk_div_table can be detected, it must be
terminated with a sentinel element (.div = 0).
Fixes: 631c53478973d ("clk: Add CLPS711X clk driver")
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
---
v4:
- Change style to { /* sentinel */ }
v3:
- no changes
v2:
- Add Fixes tag
---
drivers/clk/clk-clps711x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/clk-clps711x.c b/drivers/clk/clk-clps711x.c
index a2c6486ef1708..f8417ee2961aa 100644
--- a/drivers/clk/clk-clps711x.c
+++ b/drivers/clk/clk-clps711x.c
@@ -28,11 +28,13 @@ static const struct clk_div_table spi_div_table[] = {
{ .val = 1, .div = 8, },
{ .val = 2, .div = 2, },
{ .val = 3, .div = 1, },
+ { /* sentinel */ }
};
static const struct clk_div_table timer_div_table[] = {
{ .val = 0, .div = 256, },
{ .val = 1, .div = 1, },
+ { /* sentinel */ }
};
struct clps711x_clk {
--
2.34.1
next prev parent reply other threads:[~2022-02-18 0:09 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
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 ` Jonathan Neuschäfer [this message]
2022-03-12 2:16 ` [PATCH v4 4/5] clk: clps711x: " 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=20220218000922.134857-5-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=arnd@arndb.de \
--cc=f4bug@amsat.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=mturquette@baylibre.com \
--cc=mturquette@linaro.org \
--cc=sboyd@kernel.org \
--cc=shc_work@mail.ru \
/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).