Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Sat, 26 Feb 2022 13:40:19 +0100
From:   Jonathan =?utf-8?Q?Neusch=C3=A4fer?= <j.neuschaefer@gmx.net>
To:     Stephen Boyd <sboyd@kernel.org>
Cc:     Jonathan =?utf-8?Q?Neusch=C3=A4fer?= <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[]
Message-ID: <Yhofs/PbIOmiyNIH@latitude>
References: <20220205103613.1216218-1-j.neuschaefer@gmx.net>
 <20220226010033.6C870C340E7@smtp.kernel.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="GWbHRrphQV3Bh8j/"
Content-Disposition: inline
In-Reply-To: <20220226010033.6C870C340E7@smtp.kernel.org>
Precedence: bulk


--GWbHRrphQV3Bh8j/
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 25, 2022 at 05:00:31PM -0800, Stephen Boyd wrote:
> Quoting Jonathan Neusch=C3=A4fer (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.
> >=20
> > In version 2 I'm addressing two warnings in the clk-lpc18xx-cgu driver
> > that I previously missed.
>=20
> 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

--GWbHRrphQV3Bh8j/
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEvHAHGBBjQPVy+qvDCDBEmo7zX9sFAmIaH3sACgkQCDBEmo7z
X9tEmxAAg6PisgpZidLLoo82mF12b0fO+MC4qfoTWHjrtx4lx8uEtEudcstu8uN4
u8CMwvh6ddSkLpAQ/Z6BakRswvdIyzS5/lENKd8qhmoP5nw+3eBMZI7HFMD7mZY5
6HywEIVzSOUXorZdWyRKTvqQt9pNfa8k1sDTpd1KDuFn6FE63lDhkbxtqiOV1m0W
JJC+dP9v2EVJsxpZVsXX0wEhT3WRScqH1JbVtzO0nkB5Zb3cx8hcDB4qyfdUlSMT
uZjn8WGOvk9RsHtlbnRsFRDMrv9ilYPaUnRXbdVuUvIAHmp+eQWEcS2E0EW6WO+M
9KJIafgjGTZZSesadNIkPafeXC2RcH/Ip54ZPTLuxKuNVCE6SjXjrdiRdfBCs5WG
f2a+mY+k65+ZLe67RvlbYQjx/w6sQIJQfdSVFn0NFQC1v6K1DPqwuzXCKnKM8P+m
QwOHDo2mveVLdMWql5+/eAL5dM/vAW5ywhGPspc3hYV2VN6X1NrgR9zHHPfTIfpZ
m8dMwI+8zJ4PrAwR/lfFTk1rqgPoSvH+w1/9TnMIfhUAeMzRRXvBBBVqLHpDaRv8
FKIwmgapLGG8+9WINeR8N0Py44L1I7/kSgFz6nvQ1eC7ghluekXao2V3GUZcyRCq
Vm35ObsxNs3bADTMlDnp/Si+gIgAr+uaLQJw4TkpMUgfsFsqM3c=
=4z9e
-----END PGP SIGNATURE-----

--GWbHRrphQV3Bh8j/--