From: Ben Hutchings <ben@decadent.org.uk>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: Walter Goldens <goldenstranger@yahoo.com>,
596626@bugs.debian.org, 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 14:00:53 +0100 [thread overview]
Message-ID: <1305291653.4065.437.camel@localhost> (raw)
In-Reply-To: <BANLkTim75f2p8wXyfeoz02asRd+Qm9aepA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
On Fri, 2011-05-13 at 09:17 +0200, Ivo Van Doorn wrote:
> Hi,
>
> >> > 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).
>
> The patch has been send upstream, it has been in wireless-next-2.6.git
> since April 19...
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commit;h=ce2919c9fffe2aa52f9c3e327176d03764dbf9b5
> The patch depends on the RT53xx support patch which was also intented
> for 2.6.40.
What is it, RT35XX or RT53XX?!
> > 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.
>
> True, but the normal flow for new features and hardware support is that they
> should be properly merged during the normal merge window. The addition
> of support of RT53xx is not something that should go to stable@kernel.org...
I understand that.
Ben.
> Patches from rt2x00.git are quite quickly send from rt2x00.git to upstream,
> and patches which are not send upstream directly have a reason for not being
> send at that time (Usually it means that it requires some extra testing).
>
> Ivo
>
--
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 --]
next prev parent reply other threads:[~2011-05-13 13:01 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 ` Bug#596626: " Ben Hutchings
2011-05-13 7:17 ` Ivo Van Doorn
2011-05-13 13:00 ` Ben Hutchings [this message]
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=1305291653.4065.437.camel@localhost \
--to=ben@decadent.org.uk \
--cc=596626@bugs.debian.org \
--cc=goldenstranger@yahoo.com \
--cc=gsimmons@gsimmons.org \
--cc=ivdoorn@gmail.com \
--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).