linux-kernel - 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]

Date:   Mon, 2 Oct 2017 15:22:24 -0400
From:   bfields@...ldses.org (J. Bruce Fields)
To:     Greg KH <greg@...ah.com>
Cc:     Jérémy Lefaure <jeremy.lefaure@....epita.fr>,
        "Tobin C. Harding" <me@...in.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 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@...in.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.