From: Greg KH <gregkh@suse.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Darren Salt <linux@youmustbejoking.demon.co.uk>
Subject: Re: [PATCH 0/3] Fix rt28{6,7}0sta to use firmware loader
Date: Mon, 13 Apr 2009 19:24:18 -0700 [thread overview]
Message-ID: <20090414022418.GA17760@suse.de> (raw)
In-Reply-To: <1239667961.18110.166.camel@deadeye.i.decadent.org.uk>
On Tue, Apr 14, 2009 at 01:12:41AM +0100, Ben Hutchings wrote:
> On Sun, 2009-04-12 at 19:44 -0700, Greg KH wrote:
> > On Mon, Apr 13, 2009 at 03:33:12AM +0100, Ben Hutchings wrote:
> > > Greg,
> > >
> > > The Ralink drivers rt2860sta, rt2870sta and rt3070sta contain non-free
> > > firmware which should be distributed separately.
> >
> > Where is it now distributed? I don't want to break people's machines
> > that were working before this patch is applied.
>
> The canonical source is
> <http://www.ralinktech.com/ralink/Home/Support/Linux.html>
Yes, and that is where I got the code that is in the driver tree that
you are objecting to now :)
> The files are now also in the Debian repository for our firmware-nonfree
> package and in <http://git.decadent.org.uk/git/linux-firmware.git>.
> I've asked David Woodhouse to pull from that into his linux-firmware.git
> so that they get into other distros.
When David pulls it into his tree, and does a release, please let me
know and I'll be glad to accept your patch. Until then, I can't accept
this patch as it would break people's machines that were previously
working.
thanks,
greg k-h
next prev parent reply other threads:[~2009-04-14 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 2:33 [PATCH 0/3] Fix rt28{6,7}0sta to use firmware loader Ben Hutchings
2009-04-13 2:44 ` Greg KH
2009-04-14 0:12 ` Ben Hutchings
2009-04-14 2:24 ` Greg KH [this message]
2009-04-20 10:19 ` David Woodhouse
2009-04-22 23:13 ` 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=20090414022418.GA17760@suse.de \
--to=gregkh@suse.de \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@youmustbejoking.demon.co.uk \
/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