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:   Thu, 8 Jun 2017 21:39:17 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc:     David Miller <davem@...emloft.net>,
        Kyle McMartin <kyle@...nel.org>,
        Kalle Valo <kvalo@...eaurora.org>, postmaster@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Daniel Wagner <wagi@...om.org>,
        David Woodhouse <dwmw2@...radead.org>,
        Arend Van Spriel <arend.vanspriel@...adcom.com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        "Li, Yi" <yi1.li@...ux.intel.com>, atull@...nel.org,
        Moritz Fischer <moritz.fischer@...us.com>,
        Petr Mladek <pmladek@...e.com>,
        Johannes Berg <johannes.berg@...el.com>,
        Emmanuel Grumbach <emmanuel.grumbach@...el.com>,
        Luciano Coelho <luciano.coelho@...el.com>,
        Andy Lutomirski <luto@...nel.org>,
        Kees Cook <keescook@...omium.org>,
        "AKASHI, Takahiro" <takahiro.akashi@...aro.org>,
        David Howells <dhowells@...hat.com>,
        Peter Jones <pjones@...hat.com>,
        Hans de Goede <hdegoede@...hat.com>,
        Alan Cox <alan@...ux.intel.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Tom Gundersen <teg@...m.no>
Subject: Re: New vger mailing list request - linux-firmware

On Thu, Jun 08, 2017 at 12:06:55PM -0700, Luis R. Rodriguez wrote:
> On Thu, Jun 8, 2017 at 11:09 AM, David Miller <davem@...emloft.net> wrote:
> > From: "Luis R. Rodriguez" <mcgrof@...nel.org>
> > Date: Thu, 8 Jun 2017 18:19:42 +0200
> >
> >> On Thu, Jun 08, 2017 at 02:53:22PM +0300, Kalle Valo wrote:
> >>> "Luis R. Rodriguez" <mcgrof@...nel.org> writes:
> >>>
> >>> > Dear vger postmaster,
> >>> >
> >>> > I think its time for a linux-firmware mailing list. If one is possible
> >>> > on vger that'd be great, otherwise let me know and I can look for an
> >>> > alternative outlet.
> >>> >
> >>> > I've been giving linux-firmware some good love as of late. One of the
> >>> > issues I have seen with old commits had been lack of eyeball reviews,
> >>> > and and also ensuring the "right people" do review and get CC'd. While
> >>> > I do tend to CC everyone and their mom, its easy for me to know who
> >>> > should be as I'm maintaining the code now -- but I see some folks fail
> >>> > to capture everyone I know should be reviewing things or might like to
> >>> > get Cc'd on such topics. Tools like checkpatch help but its not
> >>> > perfect and now everyone use it. Instead of CC'ing everyone I know
> >>> > should be Cc'd on linux-firmware stuff I think its time for a proper
> >>> > mailing list for it.
> >>> >
> >>> > This should also help with reviewing old patches and letting new folks
> >>> > engage more easily by looking at specific dedicate archive of what's
> >>> > going on.
> >>>
> >>> There's already linux-firmware@...nel.org (an alias I think, not sure)
> >>
> >> Ah, yes thanks.
> >>
> >>> for submitting patches to linux-firmware.git. I think it will be
> >>> confusing if we will have two separate linux-firmware destinations under
> >>> kernel.org domain:
> >>>
> >>> linux-firmware@...nel.org
> >>> linux-firmware@...r.kernel.org
> >>>
> >>> Maybe rename the new list to linux-fw-dev@...r.kernel.org or something
> >>> like that to make it more obvious which one is which?
> >>
> >> Yeah good call. That's fine by me, but I'll leave it to postmaster to
> >> also decide.
> >
> > One list is enough, I think.
> 
> Oh, thing is linux-firmware@...nel.org is for patches to the
> linux-firmare.git tree, meanwhile my request was for
> drivers/base/firmware_class.c, its respective headers and
> documentation. I really don't think folks who want to see changes to
> the firmware_class changes want to see any of the binary blobs that go
> into linux-firmware.git.

Does a single file, or just a few files, really need a whole new mailing
list?  I don't think so, let's just stick with lkml for now.

thanks

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ