From: Stephen Boyd <sboyd@kernel.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linux-clk@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [PATCH v2 0/7] clk: Declare mux tables as const u32[]
Date: Fri, 25 Feb 2022 17:00:31 -0800 [thread overview]
Message-ID: <20220226010033.6C870C340E7@smtp.kernel.org> (raw)
In-Reply-To: <20220205103613.1216218-1-j.neuschaefer@gmx.net>
Quoting Jonathan Neuschäfer (2022-02-05 02:36:06)
> I noticed that the 'table' parameter to clk_register_mux_table is never
> used for modifying the table elements, and so it can be declared const.
>
> In version 2 I'm addressing two warnings in the clk-lpc18xx-cgu driver
> that I previously missed.
The format of these patches deeply confused my scripts that use git
interpret-trailer. I fixed it now, hopefully it keeps working. In the
future, please don't add more triple dash '---' sections to the patch.
It looks like those extra sections for the changelog messed everything
up. Or there's a new bug in interpret-trailers. Either way,
interpret-trailers was adding tags after the entire patch contents
because I think it looks for the last triple dash instead of the first
triple dash. Not sure why it's done that way. I resorted to
reconstructing the patch after splitting it with mailinfo.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-26 1:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 10:36 [PATCH v2 0/7] clk: Declare mux tables as const u32[] Jonathan Neuschäfer
2022-02-05 10:36 ` [PATCH v2 1/7] clk: nxp: Remove unused variable Jonathan Neuschäfer
2022-02-26 1:00 ` Stephen Boyd
2022-02-05 10:36 ` [PATCH v2 2/7] clk: nxp: Declare mux table parameter as const u32 * Jonathan Neuschäfer
2022-02-26 1:00 ` Stephen Boyd
2022-02-05 10:36 ` [PATCH v2 3/7] clk: mux: Declare u32 *table parameter as const Jonathan Neuschäfer
2022-02-26 1:01 ` Stephen Boyd
2022-02-05 10:36 ` [PATCH v2 4/7] clk: hisilicon: Remove unnecessary cast of mux table to u32 * Jonathan Neuschäfer
2022-02-26 1:01 ` Stephen Boyd
2022-02-05 10:36 ` [PATCH v2 5/7] clk: mmp: Declare mux tables as const u32[] Jonathan Neuschäfer
2022-02-26 1:01 ` Stephen Boyd
2022-02-05 10:36 ` [PATCH v2 6/7] clk: qcom: Declare mux table " Jonathan Neuschäfer
2022-02-26 1:02 ` Stephen Boyd
2022-02-05 10:36 ` [PATCH v2 7/7] clk: pistachio: " Jonathan Neuschäfer
2022-02-26 1:02 ` Stephen Boyd
2022-02-26 1:00 ` Stephen Boyd [this message]
2022-02-26 12:40 ` [PATCH v2 0/7] clk: Declare mux tables " Jonathan Neuschäfer
2022-03-12 2:33 ` 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=20220226010033.6C870C340E7@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).