[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85df8c40-dac9-5f97-f81a-6de061cfdfa8@kernel.dk>
Date: Wed, 11 Jul 2018 13:31:51 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Daniel Vetter <daniel.vetter@...ll.ch>
Cc: Tejun Heo <tj@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
DRI Development <dri-devel@...ts.freedesktop.org>,
Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
Daniel Vetter <daniel.vetter@...el.com>,
Shaohua Li <shli@...com>,
Kate Stewart <kstewart@...uxfoundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joseph Qi <joseph.qi@...ux.alibaba.com>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 02/12] blk: use for_each_if
On 7/11/18 12:50 PM, Daniel Vetter wrote:
> On Wed, Jul 11, 2018 at 8:30 PM, Jens Axboe <axboe@...nel.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.vetter@...el.com>
>>>>> Cc: Tejun Heo <tj@...nel.org>
>>>>> Cc: Jens Axboe <axboe@...nel.dk>
>>>>> Cc: Shaohua Li <shli@...com>
>>>>> Cc: Kate Stewart <kstewart@...uxfoundation.org>
>>>>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>>>>> Cc: Joseph Qi <joseph.qi@...ux.alibaba.com>
>>>>> Cc: Daniel Vetter <daniel.vetter@...ll.ch>
>>>>> Cc: Arnd Bergmann <arnd@...db.de>
>>>>
>>>> Acked-by: Tejun Heo <tj@...nel.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
> either.
>
> So what's the magic way to make this possible?
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).
--
Jens Axboe
Powered by blists - more mailing lists