From: Johannes Berg <johannes@sipsolutions.net>
To: jt@hpl.hp.com
Cc: Dan Williams <dcbw@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH] introduce WEXT scan capabilities
Date: Fri, 07 Dec 2007 22:38:06 +0100 [thread overview]
Message-ID: <1197063487.4171.26.camel@johannes.berg> (raw)
In-Reply-To: <20071207192756.GA15864@bougret.hpl.hp.com> (sfid-20071207_192851_749770_5C5B444C)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
> > > __u32 enc_capa; /* IW_ENC_CAPA_* bit field */
> > > +
> > > + /* Do *NOT* use those fields, they are just used as padding to get
> > > + * proper alignement with user space */
> > > + __s32 min_pms;
> > > + __s32 max_pms;
> > > + __u16 pms_flags;
> > > + __s32 modul_capa;
> > > + __u32 bitrate_capa;
> > > +
> > > + __u32 scan_capa; /* IW_SCAN_CAPA_* bit field */
> Those fields are defined and used in userspace, please check
> wireless.21.h in Wireless Tools.
Eww. That's absolutely tasteless.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2007-12-07 21:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 11:28 [RFC PATCH] introduce WEXT scan capabilities Dan Williams
2007-12-06 19:11 ` Jean Tourrilhes
2007-12-07 10:20 ` Dan Williams
2007-12-07 19:27 ` Jean Tourrilhes
2007-12-07 21:38 ` Johannes Berg [this message]
2007-12-07 22:19 ` Jean Tourrilhes
2007-12-07 22:27 ` Johannes Berg
2007-12-08 2:04 ` David Miller
2007-12-09 17:35 ` Dan Williams
2007-12-09 17:59 ` Dan Williams
2007-12-10 6:10 ` David Miller
2007-12-10 17:23 ` Dan Williams
2007-12-11 0:11 ` David Miller
2007-12-11 4:22 ` Dan Williams
2007-12-11 4:51 ` David Miller
2007-12-11 15:01 ` Dan Williams
2007-12-10 12:15 ` Johannes Berg
2007-12-10 18:09 ` Jean Tourrilhes
2007-12-11 0:15 ` David Miller
2007-12-11 13:21 ` Johannes Berg
2007-12-10 18:11 ` Jean Tourrilhes
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=1197063487.4171.26.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=jt@hpl.hp.com \
--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.