From: "Tobin C. Harding" <me@tobin.cc>
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,
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
Subject: Re: [PATCH 00/18] use ARRAY_SIZE macro
Date: Mon, 2 Oct 2017 09:01:31 +1100 [thread overview]
Message-ID: <20171001220131.GA11812@eros> (raw)
In-Reply-To: <20171001193101.8898-1-jeremy.lefaure@lse.epita.fr>
On Sun, Oct 01, 2017 at 03:30:38PM -0400, Jérémy Lefaure wrote:
> Hi everyone,
> Using ARRAY_SIZE improves the code readability. I used coccinelle (I
> made a change to the array_size.cocci file [1]) to find several places
> where ARRAY_SIZE could be used instead of other macros or sizeof
> division.
>
> I tried to divide the changes into a patch per subsystem (excepted for
> staging). If one of the patch should be split into several patches, let
> me know.
>
> 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).
I get that this will be more work for you but AFAIK we are optimizing for maintainers.
Good luck,
Tobin.
next prev parent reply other threads:[~2017-10-01 22:01 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 ` Tobin C. Harding [this message]
2017-10-02 0:52 ` [PATCH 00/18] use ARRAY_SIZE macro Jérémy Lefaure
2017-10-02 5:35 ` Greg KH
2017-10-02 19:22 ` J. Bruce Fields
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=20171001220131.GA11812@eros \
--to=me@tobin.cc \
--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-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=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 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).