public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Stephen Boyd <sboyd@kernel.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] clk: Declare mux tables as const u32[]
Date: Sat, 26 Feb 2022 13:40:19 +0100	[thread overview]
Message-ID: <Yhofs/PbIOmiyNIH@latitude> (raw)
In-Reply-To: <20220226010033.6C870C340E7@smtp.kernel.org>

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

On Fri, Feb 25, 2022 at 05:00:31PM -0800, Stephen Boyd wrote:
> 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.

Hmm, sorry about that.

I've used this format for a while, because it conveniently lets me
keep my remarks in a git commit (rather than a patch file), until I use
git format-patch to generate the final patch file.

I'm not very familiar with git interpret-trailers, but git 2.34.1
doesn't seem to get confused on my patches (or I didn't pass the right
options to cause it to happen).


Jonathan

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

  reply	other threads:[~2022-02-26 12:40 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 ` [PATCH v2 0/7] clk: Declare mux tables " Stephen Boyd
2022-02-26 12:40   ` Jonathan Neuschäfer [this message]
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=Yhofs/PbIOmiyNIH@latitude \
    --to=j.neuschaefer@gmx.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@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