linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Alexander Shiyan" <shc_work@mail.ru>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Mike Turquette" <mturquette@linaro.org>
Subject: Re: [PATCH v3 4/4] clk: clps711x: Terminate clk_div_table with sentinel element
Date: Sat, 5 Feb 2022 14:07:25 +0100	[thread overview]
Message-ID: <Yf52jcOQGvjWhCAL@latitude> (raw)
In-Reply-To: <df167547-a1b2-5b20-705c-33403ecf9e47@amsat.org>

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

On Sat, Feb 05, 2022 at 01:13:00PM +0100, Philippe Mathieu-Daudé wrote:
> On 5/2/22 01:52, Jonathan Neuschäfer wrote:
> > 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>
> > ---
> > 
> > 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..d96d96c8752c7 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, },
> > +	{}
> 
> Why not use the same style on all patches? Others developers looking
> at this code will directly grab this is a sentinel section, instead of
> wondering why this empty section is here.
> 
>         { /* sentinel */ }

I found the {} style sufficient.
But ok, I'll go with { /* sentinel */ } now.

> 
> Anyhow the patch logic is correct, so:
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

Thanks!

Jonathan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-02-05 13:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05  0:52 [PATCH v3 0/4] clk drivers: Terminate clk_div_table with sentinel element Jonathan Neuschäfer
2022-02-05  0:52 ` [PATCH v3 1/4] clk: actions: " Jonathan Neuschäfer
2022-02-05 12:15   ` Philippe Mathieu-Daudé
2022-02-05 12:58     ` Jonathan Neuschäfer
2022-02-05  0:52 ` [PATCH v3 2/4] clk: loongson1: " Jonathan Neuschäfer
2022-02-05 12:17   ` Philippe Mathieu-Daudé
2022-02-05 12:59     ` Jonathan Neuschäfer
2022-02-05  0:52 ` [PATCH v3 3/4] clk: hisilicon: " Jonathan Neuschäfer
2022-02-05  0:52 ` [PATCH v3 4/4] clk: clps711x: " Jonathan Neuschäfer
2022-02-05 12:13   ` Philippe Mathieu-Daudé
2022-02-05 13:07     ` Jonathan Neuschäfer [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=Yf52jcOQGvjWhCAL@latitude \
    --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).