From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Michael Buesch" <mb@bu3sch.de>,
"Stefanik Gábor" <netrolller.3d@gmail.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
cs010101@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: [Q] ath5k : doesn't support AP mode?
Date: Thu, 26 Jun 2008 14:08:08 -0400 [thread overview]
Message-ID: <1214503688.18039.9.camel@dv> (raw)
In-Reply-To: <20080626173645.GB22075@tuxdriver.com>
On Thu, 2008-06-26 at 13:36 -0400, John W. Linville wrote:
> I dunno...that last thing I want is to let this go in and then be
> locked-in to the current API no-matter-what like we now are with WEXT.
Is there any API that needs to be _changed_ (not added) for AP support?
I understand it may be hard to anticipate future needs, but some things
should be clear at this point already.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-26 19:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 2:54 [Q] ath5k : doesn't support AP mode? 김영환
2008-06-26 2:57 ` Pavel Roskin
2008-06-26 13:33 ` Johannes Berg
2008-06-26 14:57 ` Pavel Roskin
2008-06-26 15:46 ` Stefanik Gábor
2008-06-26 16:01 ` Pavel Roskin
2008-06-26 16:21 ` Michael Buesch
2008-06-26 16:34 ` Pavel Roskin
2008-06-26 16:46 ` Michael Buesch
2008-06-26 17:23 ` Johannes Berg
2008-06-26 18:03 ` Pavel Roskin
2008-06-26 18:08 ` Johannes Berg
2008-06-26 18:18 ` Pavel Roskin
2008-06-26 18:21 ` Johannes Berg
2008-06-26 18:27 ` Johannes Berg
2008-06-26 18:36 ` Pavel Roskin
2008-06-26 18:37 ` Johannes Berg
2008-06-26 18:22 ` Michael Buesch
2008-06-26 17:36 ` John W. Linville
2008-06-26 18:08 ` Pavel Roskin [this message]
2008-06-26 18:08 ` Michael Buesch
2008-06-26 17:24 ` Johannes Berg
2008-06-26 17:27 ` Johannes Berg
2008-06-26 18:09 ` Stefanik Gábor
2008-06-26 18:20 ` Johannes Berg
2008-06-26 18:34 ` Stefanik Gábor
2008-06-26 18:36 ` Johannes Berg
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=1214503688.18039.9.camel@dv \
--to=proski@gnu.org \
--cc=cs010101@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@gmail.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