From: Hauke Mehrtens <hauke@hauke-m.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Luis Rodriguez <mcgrof@frijolero.org>
Subject: Re: compat-wireless patch Re: [PATCH] Enable CONFIG_RT2800{PCI,USB}_RT53XX
Date: Tue, 03 Jan 2012 19:59:52 +0100 [thread overview]
Message-ID: <4F035028.6030207@hauke-m.de> (raw)
In-Reply-To: <20120103153535.GA24318@tuxdriver.com>
On 01/03/2012 04:35 PM, John W. Linville wrote:
> On Tue, Jan 03, 2012 at 10:28:36AM -0500, John W. Linville wrote:
>> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>> ---
>> Any reason to treat these differently than the RT35XX devices?
Some/Long time ago RT53XX devices where marked as not working in
Kconfig, now I can not find such a message any more, so I am totally
fine with this patch.
Hauke
next prev parent reply other threads:[~2012-01-03 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 15:28 [PATCH] Enable CONFIG_RT2800{PCI,USB}_RT53XX John W. Linville
2012-01-03 15:35 ` compat-wireless patch " John W. Linville
2012-01-03 18:59 ` Hauke Mehrtens [this message]
2012-01-18 19:16 ` Luis R. Rodriguez
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=4F035028.6030207@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
/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).