linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Walter Goldens <goldenstranger@yahoo.com>, 596626@bugs.debian.org
Cc: Ivo van Doorn <IvDoorn@gmail.com>,
	maximilian attems <max@stro.at>,
	linux-wireless@vger.kernel.org,
	Geoff Simmons <gsimmons@gsimmons.org>
Subject: Re: Bug#596626: [gsimmons@gsimmons.org: Bug#596626: Please support Linksys WUSB600N v2 WiFi USB stick]
Date: Fri, 13 May 2011 05:58:35 +0100	[thread overview]
Message-ID: <1305262715.4065.436.camel@localhost> (raw)
In-Reply-To: <13602.31426.qm@web161615.mail.bf1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Wed, 2011-05-11 at 09:25 -0700, Walter Goldens wrote:
> > As mentioned by Jan, the device contains a RT3572
> > chipset.  Its entry
> > could moved into the section for known RT35XX devices (i.e.
> > "#ifdef
> > CONFIG_RT2800USB_RT35XX") as an alternative.
> > 
> > Geoff
> 
> This has already been done: http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=commitdiff;h=ce2919c9fffe2aa52f9c3e327176d03764dbf9b5

That's all very well, but that isn't going to get into a stable release
for another 3 months!  Device ID updates that don't require new
supporting code should be sent upstream straight away (and cc'd to
stable@kernel.org).

I've cherry-picked this and the other two updates in rt2800usb that
aren't in Linus's tree, but that doesn't help the users of other
distributions that would benefit from them.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-05-13  4:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 14:23 [gsimmons@gsimmons.org: Bug#596626: Please support Linksys WUSB600N v2 WiFi USB stick] maximilian attems
2011-05-11 16:25 ` Walter Goldens
2011-05-13  4:58   ` Ben Hutchings [this message]
2011-05-13  7:17     ` Bug#596626: " Ivo Van Doorn
2011-05-13 13:00       ` Ben Hutchings
2011-05-13 13:05         ` Ivo Van Doorn
2011-05-13  9:12     ` Gertjan van Wingerde

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=1305262715.4065.436.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=596626@bugs.debian.org \
    --cc=IvDoorn@gmail.com \
    --cc=goldenstranger@yahoo.com \
    --cc=gsimmons@gsimmons.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=max@stro.at \
    /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;
as well as URLs for NNTP newsgroup(s).