On Tue, Feb 16, 2021 at 01:54:25AM +0900, Hector Martin wrote: > On 16/02/2021 01.12, gregkh wrote: > > On Tue, Feb 16, 2021 at 12:57:27AM +0900, Hector Martin wrote: > > > On 15/02/2021 22.22, gregkh wrote: > > > > On Mon, Feb 15, 2021 at 01:57:39PM +0100, Arnd Bergmann wrote: > > > > > (adding maintainers for the serial/irqchip/clocksource drivers and > > > > > arch/arm64 to cc) > > > > > > > > > > I would suggest merging it together as a series through the soc tree for > > > > > v5.13, once each patch has been reviewed by the respective subsystem > > > > > maintainers, with possible add-on patches on the same branch for > > > > > additional drivers that may become ready during the 5.12-rc cycle. > > > > > After the initial merge, driver patches will of course go through subsystem > > > > > trees as normal. > > > > > > > > > > Let me know if that works for everyone. > > > > > > > > Sure, as long as the maintainers get to see the patches, I don't think > > > > I've seen the serial ones at all... > > > > > > Sorry, I figured Krzysztof would take a look at it first and I didn't want > > > to spam too much. I'm still getting used to figuring out who to CC... > > > > scripts/get_maintainer.pl is your friend. > > It's the additional step of figuring out who to include from > get_maintainer.pl output, and whether any subsetting is warranted at all, > that I'm finding less well documented... :-) > > (In particular for a bring-up series such as this one, where most people are > only concerned with a few patches... but maybe I'm just overthinking things) For bigger patchsets, you should combine get_maintainer.pl with sending emails so individual patches will go to all role-based entries from get_maintainer.pl and to all mailing lists. You can (and sometimes even worth to) skip proposals based on git-history. Then the cover letter which should go to everyone... or most of people and linked from individual patches. For example the easiest I think: 1. Put all folks and lists as "Cc:" in cover letter. 2. Send everything: git send-email --cc-cmd "scripts/get_maintainer.pl --no-git --no-roles --no-rolestats" --to linux-kernel@xxxxxxxxxxxxxxx 0* Optionally you could add --no-git-fallback to get_maintainer if it proposes some irrelevant addresses. Other way is to send first cover letter and then reference it via in-reply-to: 1. To get everyone for cover letter: scripts/get_maintainer.pl --no-multiline --interactive --separator=\'' --to '\' --no-git --no-roles --no-rolestats 00* 2. git send-email --cc linux-kernel@xxxxxxxxxxxxxxx ... 0000* 3. Finally all patches with in-reply-to: git send-email --cc-cmd "scripts/get_maintainer.pl --no-git --no-roles --no-rolestats" --to linux-kernel@xxxxxxxxxxxxxxx --no-thread --in-reply-to='foo-bar-xxxxxxx' 000[123456789]-* 00[123456789]*-* Best regards, Krzysztof
