[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f06cab9a-853f-4ccf-ae4d-40e0e897ea60@lunn.ch>
Date: Mon, 12 Aug 2024 23:03:43 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Rosen Penev <rosenp@...il.com>
Cc: Simon Horman <horms@...nel.org>, netdev@...r.kernel.org,
vburru@...vell.com, sedara@...vell.com, srasheed@...vell.com,
sburla@...vell.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: octeon_ep_vf: use ethtool_sprintf/puts
> > 2. You have posed a number of similar patches.
> > To aid review it would be best to group these, say in batches of
> > no more than 10.
> I plan to do a treewide commit with a coccinelle script but would like
> to manually fix the problematic ones before doing so. Having said that
> I still need to figure out how to do a cover letter...
git format-patch --cover-letter HEAD~42
I also find `b4 prep` good for managing patchsets, and it will produce
a cover letter by default if there is more than one patch in the set:
https://b4.docs.kernel.org/en/latest/contributor/prep.html
Andrew
Powered by blists - more mailing lists