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 <[email protected]> wrote: > > From: "Luis R. Rodriguez" <[email protected]> > > 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" <[email protected]> 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 [email protected] (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: > >>> > >>> [email protected] > >>> [email protected] > >>> > >>> Maybe rename the new list to [email protected] 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 [email protected] 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
