public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: David Miller <davem@davemloft.net>,
	Kyle McMartin <kyle@kernel.org>,
	Kalle Valo <kvalo@codeaurora.org>,
	postmaster@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Daniel Wagner <wagi@monom.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Arend Van Spriel <arend.vanspriel@broadcom.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Li, Yi" <yi1.li@linux.intel.com>,
	atull@kernel.org, Moritz Fischer <moritz.fischer@ettus.com>,
	Petr Mladek <pmladek@suse.com>,
	Johannes Berg <johannes.berg@intel.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Luciano Coelho <luciano.coelho@intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	"AKASHI, Takahiro" <takahiro.akashi@linaro.org>,
	David Howells <dhowells@redhat.com>,
	Peter Jones <pjones@redhat.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Alan Cox <alan@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Tom Gundersen <teg@jklm.no>
Subject: Re: New vger mailing list request - linux-firmware
Date: Thu, 8 Jun 2017 21:39:17 +0200	[thread overview]
Message-ID: <20170608193917.GA19849@kroah.com> (raw)
In-Reply-To: <CAB=NE6UEq7O_OmLvG90rC_6GniQBY9weCnDAnwH5s=tcNofndQ@mail.gmail.com>

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@davemloft.net> wrote:
> > From: "Luis R. Rodriguez" <mcgrof@kernel.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@kernel.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@kernel.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@kernel.org
> >>> linux-firmware@vger.kernel.org
> >>>
> >>> Maybe rename the new list to linux-fw-dev@vger.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@kernel.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

  reply	other threads:[~2017-06-08 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 21:22 New vger mailing list request - linux-firmware Luis R. Rodriguez
2017-06-08 11:53 ` Kalle Valo
2017-06-08 16:19   ` Luis R. Rodriguez
2017-06-08 18:09     ` David Miller
2017-06-08 19:06       ` Luis R. Rodriguez
2017-06-08 19:39         ` Greg Kroah-Hartman [this message]
2017-06-08 20:11           ` Luis R. Rodriguez
2017-06-08 20:19             ` Linus Torvalds
2017-06-08 20:25               ` Luis R. Rodriguez
2017-06-08 20:31                 ` Greg Kroah-Hartman
2017-06-08 20:38                   ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170608193917.GA19849@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alan@linux.intel.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=atull@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=emmanuel.grumbach@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=johannes.berg@intel.com \
    --cc=keescook@chromium.org \
    --cc=kvalo@codeaurora.org \
    --cc=kyle@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=luto@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=pjones@redhat.com \
    --cc=pmladek@suse.com \
    --cc=postmaster@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=takahiro.akashi@linaro.org \
    --cc=teg@jklm.no \
    --cc=torvalds@linux-foundation.org \
    --cc=wagi@monom.org \
    --cc=yi1.li@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox