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]

Message-ID: <20171001205220.10b78086@blatinox-laptop.localdomain>
Date:   Sun, 1 Oct 2017 20:52:20 -0400
From:   Jérémy Lefaure <jeremy.lefaure@....epita.fr>
To:     "Tobin C. Harding" <me@...in.cc>
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, 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.

As each patch in this series is standalone, the maintainers can pick
the patches they want and apply them individually. So yeah, maybe I
should have sent individual patches. But I also wanted to tie all
patches together as it's the same change.

Anyway, I can tell to each maintainer that they can apply the patches
they're concerned about and next time I may send individual patches.

Thank you for your answer,
Jérémy