From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1 V2] mac80211: add sta_notify callback
Date: Sun, 30 Sep 2007 14:28:40 +0200 [thread overview]
Message-ID: <1191155320.22960.155.camel@johannes.berg> (raw)
In-Reply-To: <1191153157853-git-send-email-tomas.winkler@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Sun, 2007-09-30 at 13:52 +0200, Tomas Winkler wrote:
> This patch adds sta_notify callback and removes sta_table_notification
> which was not used by any driver.
> sta_notify() is essential for drivers that keeps notion of station
> internally and need to be notified about removal or addition of a station
> to the (I)BSS or assocation to an AP.
Looks good to me.
> This version adds interface id to the parameter list
> as suggested by Johannes Berg
I think I created a problem with this, see below.
> + if (local->ops->sta_notify)
> + local->ops->sta_notify(local_to_hw(local), sta->dev->ifindex,
> + STA_NOTIFY_REMOVE, sta->addr);
Never thought about this before, but "dev" could be a VLAN at this point
so the if index will be useless.
However, since we don't have per-IF stations right now this patch is
fine with me, I'll just have to remember to fix this call when I add
per-IF stations and drivers might start to care.
Acked-by: Johannes Berg <johannes@sipsolutions.net>
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2007-09-30 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 11:52 [PATCH 1/1 V2] mac80211: add sta_notify callback Tomas Winkler
2007-09-30 12:28 ` Johannes Berg [this message]
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=1191155320.22960.155.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.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