From: "Stephen Gutknecht (hilltx)" <stephen@hilltx.com>
To: linux-wireless@vger.kernel.org
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [PATCH 00/15] ath9k: Virtual interfaces and radios
Date: Tue, 10 Mar 2009 05:43:31 -0700 [thread overview]
Message-ID: <eef88e5b0903100543l22622769u5951003099eef312@mail.gmail.com> (raw)
Howdy Jouni,
I agree with Florian Fainelli. As a user of ath9k I would love to see
these patches make it into the driver. I've not seen technical
complaints of your patches. Time to rebase and get them included? Or
at least some testing reports?
I'm sure OpenWrt users would love this.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Gutknecht (hilltx) <stephen@hilltx.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 00/15] ath9k: Virtual interfaces and radios
Date: Tue, 10 Mar 2009 05:43:31 -0700 [thread overview]
Message-ID: <eef88e5b0903100543l22622769u5951003099eef312@mail.gmail.com> (raw)
Howdy Jouni,
I agree with Florian Fainelli. As a user of ath9k I would love to see
these patches make it into the driver. I've not seen technical
complaints of your patches. Time to rebase and get them included? Or
at least some testing reports?
I'm sure OpenWrt users would love this.
next reply other threads:[~2009-03-10 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 12:43 Stephen Gutknecht (hilltx) [this message]
2009-03-10 12:43 ` [ath9k-devel] [PATCH 00/15] ath9k: Virtual interfaces and radios Stephen Gutknecht
2009-03-10 17:03 ` Jouni Malinen
2009-03-10 17:03 ` [ath9k-devel] " Jouni Malinen
2009-03-10 17:23 ` Johannes Berg
2009-03-10 17:23 ` [ath9k-devel] " Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2009-03-03 17:23 Jouni Malinen
2009-03-07 13:56 ` Florian Fainelli
2009-03-12 20:19 ` Jouni Malinen
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=eef88e5b0903100543l22622769u5951003099eef312@mail.gmail.com \
--to=stephen@hilltx.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.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.