netdev - Re: [PATCH 00/18] use ARRAY

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171001220131.GA11812@eros>
Date:   Mon, 2 Oct 2017 09:01:31 +1100
From:   "Tobin C. Harding" <me@...in.cc>
To:     Jérémy Lefaure <jeremy.lefaure@....epita.fr>
Cc:     alsa-devel@...a-project.org, nouveau@...ts.freedesktop.org,
        dri-devel@...ts.freedesktop.org, dm-devel@...hat.com,
        brcm80211-dev-list@...ress.com, devel@...verdev.osuosl.org,
        linux-scsi@...r.kernel.org, linux-rdma@...r.kernel.org,
        amd-gfx@...ts.freedesktop.org,
        Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
        linux-acpi@...r.kernel.org, linux-video@...ey.karlin.mff.cuni.cz,
        intel-wired-lan@...ts.osuosl.org, linux-media@...r.kernel.org,
        intel-gfx@...ts.freedesktop.org, ecryptfs@...r.kernel.org,
        linux-nfs@...r.kernel.org, linux-raid@...r.kernel.org,
        openipmi-developer@...ts.sourceforge.net,
        intel-gvt-dev@...ts.freedesktop.org, devel@...ica.org,
        brcm80211-dev-list.pdl@...adcom.com, netdev@...r.kernel.org,
        linux-usb@...r.kernel.org, linux-wireless@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org
Subject: Re: [PATCH 00/18] use ARRAY_SIZE macro

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.