Linux wireless drivers development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, jt@hpl.hp.com
Subject: Re: linux/wireless.h - missing section
Date: Wed, 27 Feb 2008 13:26:13 -0500	[thread overview]
Message-ID: <20080227182613.GE3078@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240802270940te95e776n4958ff6b9f5beb20@mail.gmail.com>

On Wed, Feb 27, 2008 at 07:40:07PM +0200, Tomas Winkler wrote:
> Does anybody knows why this section is missing from in kernel linux/wireless.h
> 
> struct iw_range {
> 
> ......
> 
> 
>         /* More power management stuff */
>         __s32           min_pms;        /* Minimal PM saving */
>         __s32           max_pms;        /* Maximal PM saving */
>         __u16           pms_flags;      /* How to decode max/min PM saving */
> 
>         /* All available modulations for driver (hw may support less) */
>         __s32           modul_capa;     /* IW_MODUL_* bit field */
> 
>         /* More bitrate stuff */
>         __u32           bitrate_capa;   /* Types of bitrates supported */
> };

Those were in Jean's original WE-21 patch.  They got
dropped in the redacted version of WE-21 I applied in commit
baef186519c69b11cf7e48c26e75feb1e6173baa.  Please see these threads:

	http://marc.info/?l=linux-netdev&m=115689985827349&w=2
	http://marc.info/?l=linux-netdev&m=115757728300747&w=2

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2008-02-27 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 17:40 linux/wireless.h - missing section Tomas Winkler
2008-02-27 17:46 ` Jean Tourrilhes
2008-02-27 17:57 ` Pavel Roskin
2008-02-27 18:26 ` John W. Linville [this message]
2008-02-27 19:23   ` Tomas Winkler

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=20080227182613.GE3078@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox