From: Johannes Berg <johannes@sipsolutions.net>
To: Ron Rindzonski <rindjon@googlemail.com>
Cc: Tomas Winkler <tomasw@gmail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Ron Rindjunsky <ron.rindjunsky@intel.com>
Subject: Re: [PATCH 1/1] mac80211: adding bss_config to low driver ops
Date: Tue, 23 Oct 2007 11:59:05 +0200 [thread overview]
Message-ID: <1193133545.9793.53.camel@johannes.berg> (raw)
In-Reply-To: <c85cb4470710230045j71339683n10d9807ea23104b3@mail.gmail.com> (sfid-20071023_084547_476398_85AED46D)
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Tue, 2007-10-23 at 09:45 +0200, Ron Rindzonski wrote:
> I can see that this structure can be a powerful way to convey
> association data internaly inside mac80211,
> and we will examine this possibility, but our initial primary
> purpose is not to replace existing data exchange
> inside mac80211, but rather to unite data exchange with low level
> driver concerning changing BSS parameters
> such as association state,erp,wmm (and HT in near future), all may
> vary during BSS lifespan, yet all have their
> own ops right now, which complicates tracking them.
Yes, I understand, my main concern with building the structure on the
fly as you've been doing is that drivers are handed a data structure
that is only partially valid which might lead to confusion. That said, I
do understand that it would be significantly more work to make mac80211
use the same structure internally, so if you're unable to do that work
somebody else will have to pick it up at some point.
> I will send you another RFC in this spirit, with your remarks from
> this thread.
Thanks,
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2007-10-23 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 23:51 [PATCH 1/1] mac80211: adding bss_config to low driver ops Tomas Winkler
2007-10-18 0:06 ` Tomas Winkler
2007-10-18 1:38 ` Michael Wu
2007-10-21 11:23 ` Rindjunsky, Ron
2007-10-18 16:48 ` Johannes Berg
2007-10-18 18:46 ` Tomas Winkler
2007-10-18 18:57 ` Johannes Berg
2007-10-19 12:25 ` Johannes Berg
[not found] ` <c85cb4470710230045j71339683n10d9807ea23104b3@mail.gmail.com>
2007-10-23 9:59 ` Johannes Berg [this message]
2007-10-19 12:20 ` 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=1193133545.9793.53.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rindjon@googlemail.com \
--cc=ron.rindjunsky@intel.com \
--cc=tomasw@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 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.