From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Jiri Benc <jbenc@suse.cz>, Michael Wu <flamingice@sourmilk.net>,
Daniel Drake <dsd@gentoo.org>
Subject: Re: [RFC] the recently discussed flags patch
Date: Tue, 14 Aug 2007 18:48:57 +0200 [thread overview]
Message-ID: <200708141848.57809.mb@bu3sch.de> (raw)
In-Reply-To: <1187108515.4037.3.camel@johannes.berg>
On Tuesday 14 August 2007 18:21:55 Johannes Berg wrote:
> +/*
> + * flags for change_filter_flags()
> + *
> + * Note that e.g. if PROMISC_IN_BSS is unset then
> + * you should still do MAC address filtering if
> + * possible even if OTHER_BSS is set to indicate
> + * no BSSID filtering should be done.
> + */
> +#define FIF_PROMISC_IN_BSS 0x01
> +#define FIF_ALLMULTI 0x02
> +#define FIF_FCSFAIL 0x04
> +#define FIF_PLCPFAIL 0x08
> +#define FIF_CONTROL 0x10
> +#define FIF_OTHER_BSS 0x20
Please some more comments on what they actually mean
and what's usually to do when the flag is set.
> + /* Change filter flags, see above for FIF_* constants.
> + *
> + * Must be atomic due to running under the tx lock.
> + * This callback is required.
> + */
> + void (*change_filter_flags)(struct ieee80211_hw *hw,
> + int changed_flags, int total_flags);
Better use unsigned int.
What does changed_flags and total_flags mean?
I thought we'd like to have a pointer here, to the driver
can clear what's not supported.
--
Greetings Michael.
next prev parent reply other threads:[~2007-08-14 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 16:21 [RFC] the recently discussed flags patch Johannes Berg
2007-08-14 16:48 ` Michael Buesch [this message]
2007-08-15 10:38 ` Johannes Berg
2007-08-14 22:56 ` Johannes Berg
2007-08-15 10:54 ` 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=200708141848.57809.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).