mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kilroy <kilroyd@googlemail.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, pe1dnn@amsat.org
Subject: Re: [PATCH 3/3] staging: wlags49_h2: Declare support for WEXT 21
Date: Mon, 19 Sep 2011 21:44:33 +0100	[thread overview]
Message-ID: <4E77A9B1.1040107@gmail.com> (raw)
In-Reply-To: <15411.1316463771@turing-police.cc.vt.edu>

On 19/09/2011 21:22, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 19 Sep 2011 21:08:16 BST, David Kilroy said:
>> There may be a few areas where we don't actually support WE21,
>> but by doing this it will make it easier to find those places.
>
> I'll bite - what happens when we find such a place?  Kernel fails to build, or
> user has a suboptimal usage experience, or?

The user would have a sub-optimal experience. iwconfig may not display a 
few things correctly (ESSID?) in particular scenarios.

The reason I included this patch was that I'm not sure whether 
wpa-supplicant requires WEXT version to be above a certain threshold to 
use the events in the previous patch. I'm happy to drop this one if it 
just works.

> What are the expected chances that sticking this in linux-next for a cycle will
> result in most/all of the places being found before this all appears in an
> official release?  I'm thinking this should probably go in linux-next right after
> the next merge window closes, to maximize the chances we'll shake it
> all out during almost 2 cycles before it hits the streets. (And yes, I know
> it's a staging/ driver - if somebody else says "one cycle is more than enough"
> I'm OK with that too...)

This hardware is old, and as far as I can tell quite rare. I'd hope we 
can get some feedback from Henk on the series before applying this patch.

Thanks,

Dave.

  reply	other threads:[~2011-09-19 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 20:08 [PATCH 0/3] staging: wlags49_h2: Improve WEXT support David Kilroy
2011-09-19 20:08 ` [PATCH 1/3] staging: wlags49_h2: Remove old WIRELESS_EXT support David Kilroy
2011-09-19 20:08 ` [PATCH 2/3] staging: wlags49_h2: Support standard WEXT events David Kilroy
2011-09-19 20:08 ` [PATCH 3/3] staging: wlags49_h2: Declare support for WEXT 21 David Kilroy
2011-09-19 20:22   ` Valdis.Kletnieks
2011-09-19 20:44     ` Dave Kilroy [this message]
2011-09-20 19:52       ` Greg KH
2011-09-20 20:15         ` Henk de Groot
2011-09-20 21:02           ` Greg KH
2011-09-21 17:58             ` Henk de Groot
2011-09-21 18:20               ` Greg KH
2011-09-21 18:26                 ` Dave Kilroy

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=4E77A9B1.1040107@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pe1dnn@amsat.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

Powered by JetHome