From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH 02/12] blk: use for_each_if Date: Wed, 11 Jul 2018 13:06:41 -0700 Message-ID: <20180711200641.GJ72677@devbig577.frc2.facebook.com> References: <20180709083650.23549-1-daniel.vetter@ffwll.ch> <20180709083650.23549-2-daniel.vetter@ffwll.ch> <20180711164058.GC72677@devbig577.frc2.facebook.com> <20180711164536.GD72677@devbig577.frc2.facebook.com> <965184f9-e5ed-3c8b-bfd7-a033a252371b@kernel.dk> <85df8c40-dac9-5f97-f81a-6de061cfdfa8@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <85df8c40-dac9-5f97-f81a-6de061cfdfa8@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org To: Jens Axboe Cc: Daniel Vetter , LKML , DRI Development , Intel Graphics Development , Daniel Vetter , Shaohua Li , Kate Stewart , Greg Kroah-Hartman , Joseph Qi , Arnd Bergmann List-Id: dri-devel@lists.freedesktop.org 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). 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. Thanks. -- tejun