Re: [PATCH v2 net-next 01/15] net: mdio-regmap: permit working with non-MMIO regmaps
From: Vladimir Oltean <vladimir.oltean@nxp.com>
Date: 2026-01-22 12:22:02
Also in:
linux-devicetree, lkml
On Thu, Jan 22, 2026 at 12:16:35PM +0000, Russell King (Oracle) wrote:
On Thu, Jan 22, 2026 at 02:13:01PM +0200, Vladimir Oltean wrote:quoted
On Thu, Jan 22, 2026 at 02:06:23PM +0200, Andy Shevchenko wrote:quoted
quoted
Cc: Mark Brown <broonie@kernel.org> Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>FWIW, Cc list may be located after --- line. It will have the same effect on emails (as regular tooling will parse and put them into email headers), but will reduce unneeded noise in the commit message. List will be still available on lore.kernel.org in the mail archives.Thanks for the comment. I know it may be located after ---, but for me, doing that implies an extra step which I find unnecessary (moving them there after the git format-patch stage). I keep the Cc: in the commit message in git so that it's preserved across revisions.What I do with my individual patch versioning is in the editor, after my sign-off, add the "---" and put the version changes below. This means git format-patch will do what it normally does, and as the commit message is reproduced verbatum, you get all that included too. You do get an extra "---" line between the versioning changes and the diffstat, but that's fine. So in the commit message: Signed-off-by: ... --- Cc: ... Changes v2: ... will work fine.
Oh, that's quite a clever use. I can now keep my changelog in git too... Thanks for the hint!