linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Greg KH <greg@kroah.com>
Cc: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>,
	"Tobin C. Harding" <me@tobin.cc>,
	alsa-devel@alsa-project.org, nouveau@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, dm-devel@redhat.com,
	brcm80211-dev-list@cypress.com, devel@driverdev.osuosl.org,
	linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
	amd-gfx@lists.freedesktop.org,
	"Jason Gunthorpe" <jgunthorpe@obsidianresearch.com>,
	linux-acpi@vger.kernel.org, linux-video@atrey.karlin.mff.cuni.cz,
	intel-wired-lan@lists.osuosl.org, linux-media@vger.kernel.org,
	intel-gfx@lists.freedesktop.org, ecryptfs@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-raid@vger.kernel.org,
	openipmi-developer@lists.sourceforge.net,
	intel-gvt-dev@lists.freedesktop.org, devel@acpica.org,
	brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH 00/18] use ARRAY_SIZE macro
Date: Mon, 2 Oct 2017 15:22:24 -0400	[thread overview]
Message-ID: <20171002192224.GD1903@fieldses.org> (raw)
In-Reply-To: <20171002053554.GA28743@kroah.com>

On Mon, Oct 02, 2017 at 07:35:54AM +0200, Greg KH wrote:
> On Sun, Oct 01, 2017 at 08:52:20PM -0400, Jérémy Lefaure wrote:
> > On Mon, 2 Oct 2017 09:01:31 +1100
> > "Tobin C. Harding" <me@tobin.cc> wrote:
> > 
> > > > In order to reduce the size of the To: and Cc: lines, each patch of the
> > > > series is sent only to the maintainers and lists concerned by the patch.
> > > > This cover letter is sent to every list concerned by this series.  
> > > 
> > > Why don't you just send individual patches for each subsystem? I'm not a maintainer but I don't see
> > > how any one person is going to be able to apply this whole series, it is making it hard for
> > > maintainers if they have to pick patches out from among the series (if indeed any will bother
> > > doing that).
> > Yeah, maybe it would have been better to send individual patches.
> > 
> > From my point of view it's a series because the patches are related (I
> > did a git format-patch from my local branch). But for the maintainers
> > point of view, they are individual patches.
> 
> And the maintainers view is what matters here, if you wish to get your
> patches reviewed and accepted...

Mainly I'd just like to know which you're asking for.  Do you want me to
apply this, or to ACK it so someone else can?  If it's sent as a series
I tend to assume the latter.

But in this case I'm assuming it's the former, so I'll pick up the nfsd
one....

--b.

  reply	other threads:[~2017-10-02 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 19:30 [PATCH 00/18] use ARRAY_SIZE macro Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 07/18] scsi: bfa: use ARRAY_SIZE Jérémy Lefaure
2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding
2017-10-02  0:52   ` Jérémy Lefaure
2017-10-02  5:35     ` Greg KH
2017-10-02 19:22       ` J. Bruce Fields [this message]
2017-10-03  1:33         ` Jérémy Lefaure
2017-10-05 17:57           ` J. Bruce Fields
2017-10-02 16:37     ` Mauro Carvalho Chehab
2017-10-02 17:05 ` Zhi Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171002192224.GD1903@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211-dev-list@cypress.com \
    --cc=devel@acpica.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dm-devel@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ecryptfs@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeremy.lefaure@lse.epita.fr \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-video@atrey.karlin.mff.cuni.cz \
    --cc=me@tobin.cc \
    --cc=nouveau@lists.freedesktop.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).