On Wed, Jul 11, 2018 at 8:30 PM, Jens Axboe <ax...@kernel.dk> wrote:
> On 7/11/18 10:45 AM, Tejun Heo wrote:
>> On Wed, Jul 11, 2018 at 09:40:58AM -0700, Tejun Heo wrote:
>>> On Mon, Jul 09, 2018 at 10:36:40AM +0200, Daniel Vetter wrote:
>>>> Makes the macros resilient against if {} else {} blocks right
>>>> afterwards.
>>>> Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
>>>> Cc: Tejun Heo <t...@kernel.org>
>>>> Cc: Jens Axboe <ax...@kernel.dk>
>>>> Cc: Shaohua Li <s...@fb.com>
>>>> Cc: Kate Stewart <kstew...@linuxfoundation.org>
>>>> Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
>>>> Cc: Joseph Qi <joseph...@linux.alibaba.com>
>>>> Cc: Daniel Vetter <daniel.vet...@ffwll.ch>
>>>> Cc: Arnd Bergmann <a...@arndb.de>
>>> Acked-by: Tejun Heo <t...@kernel.org>
>>> Jens, it'd probably be best to route this through block tree.
>> Oops, this requires an earlier patch to move the for_each_if def to a
>> common header and should be routed together.
> Yeah, this is a problem with the submission.
> Always (ALWAYS) CC folks on at least the cover letter and generic
> earlier patches. Getting just one patch sent like this is mostly
> useless, and causes more harm than good.

Ime sending a patch with more than 20 or so recipients means it gets
stuck everywhere in moderation queues. Or outright spam filters. I
thought the correct way to do this is to cc: mailing lists (lkml has
them all), but apparently that's not how it's done. Despite that all
the patch series I get never have the cover letter addressed to me

So what's the magic way to make this possible?
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
dri-devel mailing list

Reply via email to