All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>
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,
	brcm80211-dev-list.pdl@broadcom.com, linux-raid@vger.kernel.org,
	openipmi-developer@lists.sourceforge.net,
	intel-gvt-dev@lists.freedesktop.org, devel@acpica.org,
	linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
	"Tobin C. Harding" <me@tobin.cc>
Subject: Re: [PATCH 00/18] use ARRAY_SIZE macro
Date: Mon, 2 Oct 2017 07:35:54 +0200	[thread overview]
Message-ID: <20171002053554.GA28743@kroah.com> (raw)
In-Reply-To: <20171001205220.10b78086@blatinox-laptop.localdomain>

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...

thanks,

greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 00/18] use ARRAY_SIZE macro
Date: Mon, 2 Oct 2017 07:35:54 +0200	[thread overview]
Message-ID: <20171002053554.GA28743@kroah.com> (raw)
In-Reply-To: <20171001205220.10b78086@blatinox-laptop.localdomain>

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...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>
Cc: "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, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH 00/18] use ARRAY_SIZE macro
Date: Mon, 2 Oct 2017 07:35:54 +0200	[thread overview]
Message-ID: <20171002053554.GA28743@kroah.com> (raw)
In-Reply-To: <20171001205220.10b78086@blatinox-laptop.localdomain>

On Sun, Oct 01, 2017 at 08:52:20PM -0400, Jeremy 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...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>
Cc: "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, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH 00/18] use ARRAY_SIZE macro
Date: Mon, 2 Oct 2017 07:35:54 +0200	[thread overview]
Message-ID: <20171002053554.GA28743@kroah.com> (raw)
In-Reply-To: <20171001205220.10b78086@blatinox-laptop.localdomain>

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...

thanks,

greg k-h

  reply	other threads:[~2017-10-02  5:35 UTC|newest]

Thread overview: 114+ 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 ` Jérémy Lefaure
2017-10-01 19:30 ` Jérémy Lefaure
2017-10-01 19:30 ` Jérémy Lefaure
2017-10-01 19:30 ` Jérémy Lefaure
2017-10-01 19:30 ` [Intel-wired-lan] " =?unknown-8bit?q?J=C3=A9r=C3=A9my?= Lefaure
2017-10-01 19:30 ` Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 01/18] sound: use ARRAY_SIZE Jérémy Lefaure
2017-10-02  4:16   ` Joe Perches
2017-10-03  1:12     ` Jérémy Lefaure
2017-10-03  1:12       ` Jérémy Lefaure
2017-10-03  7:03   ` Takashi Iwai
2017-10-03  7:03     ` Takashi Iwai
2017-10-01 19:30 ` [PATCH 02/18] tracing/filter: " Jérémy Lefaure
2017-10-04  1:05   ` Steven Rostedt
2017-10-01 19:30 ` [PATCH 03/18] media: " Jérémy Lefaure
2017-10-02 10:34   ` Michael Ira Krufky
2017-10-01 19:30 ` [PATCH 04/18] IB/mlx5: Use ARRAY_SIZE Jérémy Lefaure
     [not found]   ` <20171001193101.8898-5-jeremy.lefaure-tU7rkvAWjlwhT4uAktR2oQ@public.gmane.org>
2017-10-02  4:38     ` Leon Romanovsky
2017-10-02  4:38       ` Leon Romanovsky
2017-10-01 19:30 ` [Intel-wired-lan] [PATCH 05/18] net: use ARRAY_SIZE =?unknown-8bit?q?J=C3=A9r=C3=A9my?= Lefaure
2017-10-01 19:30   ` Jérémy Lefaure
2017-10-02 13:07   ` [Intel-wired-lan] " Andy Shevchenko
2017-10-02 13:07     ` Andy Shevchenko
2017-10-02 13:07     ` Andy Shevchenko
2017-10-02 13:07     ` Andy Shevchenko
2017-10-03  1:22     ` [Intel-wired-lan] " =?unknown-8bit?q?J=C3=A9r=C3=A9my?= Lefaure
2017-10-03  1:22       ` Jérémy Lefaure
2017-10-03  1:22       ` Jérémy Lefaure
2017-10-03  8:09       ` [Intel-wired-lan] " Andy Shevchenko
2017-10-03  8:09         ` Andy Shevchenko
2017-10-03  8:09         ` Andy Shevchenko
2017-10-03  8:09         ` Andy Shevchenko
2017-10-02 13:46   ` [Intel-wired-lan] " Kalle Valo
2017-10-02 13:46     ` Kalle Valo
2017-10-02 13:46     ` Kalle Valo
2017-10-02 13:46     ` Kalle Valo
2017-10-03  1:23     ` [Intel-wired-lan] " =?unknown-8bit?q?J=C3=A9r=C3=A9my?= Lefaure
2017-10-03  1:23       ` Jérémy Lefaure
2017-10-03  1:23       ` Jérémy Lefaure
2017-11-14  3:19   ` [PATCH v2] wireless: " Jérémy Lefaure
2017-12-08 13:20     ` [v2] " Kalle Valo
2017-11-14  3:24   ` [PATCH v2] net: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 06/18] drm: " Jérémy Lefaure
     [not found]   ` <20171001193101.8898-7-jeremy.lefaure-tU7rkvAWjlwhT4uAktR2oQ@public.gmane.org>
2017-10-02  7:43     ` Jani Nikula
2017-10-02  7:43       ` Jani Nikula
2017-10-02  8:27   ` Thierry Reding
2017-10-02  8:27     ` Thierry Reding
2017-10-01 19:30 ` [PATCH 07/18] scsi: bfa: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 08/18] ecryptfs: " Jérémy Lefaure
2017-10-14  1:31   ` Tyler Hicks
2017-10-01 19:30 ` [PATCH 09/18] nfsd: " Jérémy Lefaure
2017-10-02 11:03   ` Jeff Layton
2017-10-01 19:30 ` [PATCH 10/18] orangefs: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 11/18] dm space map metadata: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 12/18] x86: " Jérémy Lefaure
2017-10-19 14:18   ` [tip:x86/cleanups] x86: Use ARRAY_SIZE tip-bot for Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 13/18] tpm: use ARRAY_SIZE Jérémy Lefaure
2017-10-01 19:30   ` Jérémy Lefaure
2017-10-04 12:14   ` Jarkko Sakkinen
2017-10-04 12:14     ` Jarkko Sakkinen
2017-10-10 20:30     ` Jérémy Lefaure
2017-10-10 20:30       ` Jérémy Lefaure
2017-10-11 11:48       ` Jarkko Sakkinen
2017-10-11 11:48         ` Jarkko Sakkinen
2017-10-01 19:30 ` [PATCH 14/18] ipmi: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 15/18] acpi: " Jérémy Lefaure
2017-10-02 12:27   ` [Devel] " Rafael J. Wysocki
2017-10-02 12:27     ` Rafael J. Wysocki
2017-10-03  1:16     ` Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 16/18] media: staging: atomisp: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 17/18] staging: rtl8723bs: " Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 18/18] staging: rtlwifi: " Jérémy Lefaure
2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding
2017-10-01 22:01   ` Tobin C. Harding
2017-10-01 22:01   ` Tobin C. Harding
2017-10-01 22:01   ` [Intel-wired-lan] " Tobin C. Harding
2017-10-02  0:52   ` Jérémy Lefaure
2017-10-02  0:52     ` Jérémy Lefaure
2017-10-02  0:52     ` Jérémy Lefaure
2017-10-02  0:52     ` Jérémy Lefaure
2017-10-02  0:52     ` [Intel-wired-lan] " =?unknown-8bit?q?J=C3=A9r=C3=A9my?= Lefaure
2017-10-02  5:35     ` Greg KH [this message]
2017-10-02  5:35       ` Greg KH
2017-10-02  5:35       ` Greg KH
2017-10-02  5:35       ` [Intel-wired-lan] " Greg KH
2017-10-02 19:22       ` J. Bruce Fields
2017-10-02 19:22         ` J. Bruce Fields
2017-10-02 19:22         ` J. Bruce Fields
2017-10-02 19:22         ` [Intel-wired-lan] " J. Bruce Fields
2017-10-03  1:33         ` Jérémy Lefaure
2017-10-03  1:33           ` Jérémy Lefaure
2017-10-03  1:33           ` Jérémy Lefaure
2017-10-03  1:33           ` Jérémy Lefaure
2017-10-03  1:33           ` [Intel-wired-lan] " =?unknown-8bit?q?J=C3=A9r=C3=A9my?= Lefaure
2017-10-03  1:33           ` Jérémy Lefaure
2017-10-05 17:57           ` J. Bruce Fields
2017-10-05 17:57             ` J. Bruce Fields
2017-10-05 17:57             ` J. Bruce Fields
2017-10-05 17:57             ` [Intel-wired-lan] " J. Bruce Fields
2017-10-02 16:37     ` Mauro Carvalho Chehab
2017-10-02 16:37       ` Mauro Carvalho Chehab
2017-10-02 16:37       ` Mauro Carvalho Chehab
2017-10-02 16:37       ` [Intel-wired-lan] " Mauro Carvalho Chehab
2017-10-02 17:05 ` Zhi Wang
2017-10-02 17:05   ` [Intel-wired-lan] [Intel-gfx] " Zhi Wang
  -- strict thread matches above, loose matches on Subject: below --
2017-10-03 11:39 [Devel] [PATCH 15/18] acpi: use ARRAY_SIZE Rafael J. Wysocki
2017-10-03 11:39 ` Rafael J. Wysocki
2017-10-03 12:34 [Devel] " Colin Ian King
2017-10-03 12:34 ` Colin Ian King
2017-10-03 16:04 Rafael J. Wysocki
2017-10-03 16:04 ` Rafael J. Wysocki
2017-10-03 16:38 Moore, Robert
2017-10-03 16:38 ` Moore, Robert

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=20171002053554.GA28743@kroah.com \
    --to=greg@kroah.com \
    --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=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-integrity@vger.kernel.org \
    --cc=linux-kernel@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-usb@vger.kernel.org \
    --cc=linux-video@atrey.karlin.mff.cuni.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.