From: John Crispin <blogic@openwrt.org>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>
Subject: Re: [PATCH] rt2x00: make the driver build for Ralink SoC
Date: Wed, 27 Mar 2013 21:48:08 +0100 [thread overview]
Message-ID: <51535B08.2000708@openwrt.org> (raw)
In-Reply-To: <AC53EE34-1306-490A-9BB3-290434C08D1C@gmail.com>
>>> Any more word on this?
>> Gabor posted a series as RFC that would fix this properly ->
>>
>> http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2013-March/005837.html
> Yeah, and that series looks good. Unfortunately, it is too intrusive to still apply for 3.9.
>
> John L., could we get in a scheme where we apply John C.'s patch for 3.9 and then use Gabor's series for 3.10?
> Don't know how that works with making sure that this patch is reverted for 3.10.
>
> Can you coordinate, or should I help you with this?
>
Hi,
if we could apply my original 'dirty' patch as a temporary fix for 3.9,
that would be great. Its not an optimal solution but it at least makes
the code compile/work.
Gabor and myself have also accumulated a pile of other patches. In
addition to the 8 patch series that splits the pci/generic code, there
is a 20 patch series, that adds rt3662/rt3883 support, a 7 patch series
that adds rt5350 support and another 8 patches that add OF support.
I am planning to setup a git tree with all these after easter and then
send them to the list for review. Ideally these patches all make it into
3.10 as we will also be merging the remaining Ralink SoC patches via the
linux-mips tree for 3.10 (with the exception of the ethernet driver as
it will need a rewrite before I can send it upstream)
John
next prev parent reply other threads:[~2013-03-27 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 19:48 [PATCH] rt2x00: make the driver build for Ralink SoC John Crispin
2013-03-20 21:29 ` Gertjan van Wingerde
2013-03-21 7:35 ` John Crispin
2013-03-27 17:17 ` John W. Linville
2013-03-27 18:25 ` John Crispin
2013-03-27 20:38 ` Gertjan van Wingerde
2013-03-27 20:48 ` John Crispin [this message]
2013-03-29 15:02 ` Gabor Juhos
2013-03-21 18:03 ` Gabor Juhos
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=51535B08.2000708@openwrt.org \
--to=blogic@openwrt.org \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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;
as well as URLs for NNTP newsgroup(s).