From: John W. Linville <linville@tuxdriver.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now
Date: Wed, 21 Apr 2010 08:59:11 -0400 [thread overview]
Message-ID: <20100421125911.GB5072@tuxdriver.com> (raw)
In-Reply-To: <19406.24076.583237.267376@gargle.gargle.HOWL>
On Wed, Apr 21, 2010 at 07:38:12AM +0530, Sujith wrote:
> John W. Linville wrote:
> > Any feedback on this?
>
> This has already been merged.
>
> commit e92119ca88691ac2239916d31c3dcecd10867521
> Author: Sujith <Sujith.Manoharan@atheros.com>
> Date: Thu Apr 1 10:28:24 2010 +0530
>
> ath9k_htc: Add TL-WN422G v2 product ID
>
> Signed-off-by: Sujith <Sujith.Manoharan@atheros.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
:-) OK, thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Wiktor Zajas <w.zajas@gmail.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now
Date: Wed, 21 Apr 2010 08:59:11 -0400 [thread overview]
Message-ID: <20100421125911.GB5072@tuxdriver.com> (raw)
In-Reply-To: <19406.24076.583237.267376@gargle.gargle.HOWL>
On Wed, Apr 21, 2010 at 07:38:12AM +0530, Sujith wrote:
> John W. Linville wrote:
> > Any feedback on this?
>
> This has already been merged.
>
> commit e92119ca88691ac2239916d31c3dcecd10867521
> Author: Sujith <Sujith.Manoharan@atheros.com>
> Date: Thu Apr 1 10:28:24 2010 +0530
>
> ath9k_htc: Add TL-WN422G v2 product ID
>
> Signed-off-by: Sujith <Sujith.Manoharan@atheros.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
:-) OK, thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-04-21 12:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 2:43 [ath9k-devel] ath9k_htc compat-wireless tarballs should be up now Luis R. Rodriguez
2010-03-28 17:39 ` mistah
2010-03-28 18:13 ` mistah
2010-03-28 23:31 ` Luis R. Rodriguez
2010-03-28 23:32 ` Luis R. Rodriguez
2010-03-29 1:31 ` mistah
2010-03-29 2:29 ` Luis R. Rodriguez
2010-03-29 2:36 ` Yongheng Qi
2010-03-29 2:38 ` Luis R. Rodriguez
2010-03-29 2:40 ` Yongheng Qi
2010-03-29 2:48 ` mistah
2010-03-29 3:06 ` Luis R. Rodriguez
2010-03-29 4:18 ` mistah
2010-03-29 4:31 ` mistah
2010-03-29 5:40 ` Sujith
2010-03-29 19:40 ` Wiktor Zajas
2010-03-29 22:20 ` [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now Luis R. Rodriguez
2010-03-29 22:20 ` Luis R. Rodriguez
2010-03-30 15:32 ` Wiktor Zajas
2010-04-20 15:45 ` John W. Linville
2010-04-20 15:45 ` John W. Linville
2010-04-20 17:36 ` Luis R. Rodriguez
2010-04-20 17:36 ` Luis R. Rodriguez
2010-04-21 2:08 ` Sujith
2010-04-21 2:08 ` Sujith
2010-04-21 12:59 ` John W. Linville [this message]
2010-04-21 12:59 ` John W. Linville
2010-03-30 3:47 ` [ath9k-devel] ath9k_htc compat-wireless tarballs should be up now Sujith
2010-03-30 15:00 ` Dyno Fu
2010-03-31 11:16 ` Sujith
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=20100421125911.GB5072@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.