From: Greg KH <gregkh@suse.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mithlesh Thukral <mithlesh@linsyssoft.com>,
Christopher Harrer <charrer@alacritech.com>
Subject: Re: Staging: sxg: Add support to download the firmware using request_firmware()
Date: Sun, 5 Apr 2009 19:33:49 -0700 [thread overview]
Message-ID: <20090406023349.GA1314@suse.de> (raw)
In-Reply-To: <1238980795.11870.12.camel@macbook.infradead.org>
On Sun, Apr 05, 2009 at 06:19:55PM -0700, David Woodhouse wrote:
> On Sun, 2009-04-05 at 18:07 -0700, Greg KH wrote:
> > Who do we email to add this to?
>
> Clone git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git,
> add your firmware (and update the WHENCE file accordingly), and send me
> a pull request. Preferably with a Signed-off-by: from within the company
> that owns the firmware in question.
Care to document this somewhere in the kernel tree so we know about it?
> > And finally, what's wrong with adding new firmware images into the
> > firmware/ directory? What is the issue here?
>
> We're working on _removing_ this crap from the kernel source tree -- not
> adding new instances of it.
Firmware isn't "crap", it's needed by devices, and I don't see the
problem of distributing it within the kernel tree, especially when the
license of the firmware is just fine, like these files are.
> We have a separate repository in which we're collecting
> redistributable firmware images, and the distributions are moving
> towards shipping that instead of just the legacy stuff from the kernel
> tree. Add any new firmware to that repository instead, as described
> above.
Are there releases of the firmware tree published and announced
anywhere so the distros know to do this?
thanks,
greg k-h
next prev parent reply other threads:[~2009-04-06 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904051919.n35JJUUq031448@hera.kernel.org>
2009-04-06 0:41 ` Staging: sxg: Add support to download the firmware using request_firmware() David Woodhouse
2009-04-06 1:07 ` Greg KH
2009-04-06 1:19 ` David Woodhouse
2009-04-06 2:33 ` Greg KH [this message]
2009-04-06 9:10 ` Alan Cox
2009-04-06 15:26 ` Greg KH
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=20090406023349.GA1314@suse.de \
--to=gregkh@suse.de \
--cc=charrer@alacritech.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mithlesh@linsyssoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.