On Wed, Jul 11, 2018 at 10:06 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > On Wed, Jul 11, 2018 at 01:31:51PM -0600, Jens Axboe wrote: >> I don't think there's a git easy way of sending it out outside of >> just ensuring that everybody is CC'ed on everything. I don't mind >> that at all. I don't subscribe to lkml, and the patches weren't >> sent to linux-block. Hence all I see is this stand-alone patch, >> and logic would dictate that it's stand-alone (but it isn't). Hm yeah I forgot to add linux-block. But others where there's no dedicated list (or get_maintainers.pl didn't have one) also complained about not getting Cc'ed, and I can't Cc everyone for sweeping changes. > What I sometimes do is including a short blurb on each patch giving > the overview and action hints (e.g. this is part of patchset doing XYZ > and should be routed such and such). It's a bit redundant but has > worked pretty well for patchsets with dependenat & sweeping changes. Yeah I guess I can just copypaste/summarize patch 1 to all the subsequent patches, sounds like the best option. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
