Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: jeff@garzik.org
Cc: Roger While <simrw@sim-basis.de>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [git patches] net driver updates
Date: Thu, 22 Feb 2007 10:48:30 -0500	[thread overview]
Message-ID: <1172159310.5114.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20070221132754.GA4978@tuxdriver.com>

On Wed, 2007-02-21 at 08:27 -0500, John W. Linville wrote:
> On Wed, Feb 21, 2007 at 12:46:46PM +0100, Roger While wrote:
> > 
> > >
> > >Dan Williams (1):
> > >      prism54: correct assignment of DOT1XENABLE in WE-19 codepaths
> > 
> > Where did this spring from ?
> > I see no posting of this patch let alone
> > an ACK.
> > The patch is also doing rather more than the description -
> > It is inserting extra breaks into a switch statement with
> > no comment as to why.
> 
> Dan posted it to linux-wireless@vger.kernel.org on 13 Feb 2007.
> The description in the body is quoted below:

It was also posted to stable@kernel.org and accepted for 2.6.19 and
2.6.20.

Dan

> 	Correct assignment of DOT1XENABLE in WE-19 codepaths.
> 	RX_UNENCRYPTED_EAPOL = 1 really means setting DOT1XENABLE _off_, and
> 	vice versa.  The original WE-19 patch erroneously reversed that.  This
> 	patch fixes association with unencrypted and WEP networks when using
> 	wpa_supplicant.
> 	
> 	It also adds two missing break statements that, left out, could result
> 	in incorrect card configuration.
> 	
> 	Please commit to both development and stable branches.
> 
> Hth...
> 
> John


      reply	other threads:[~2007-02-22 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6.1.1.1.2.20070221124144.04783fb8@192.168.6.12>
2007-02-21 13:27 ` [git patches] net driver updates John W. Linville
2007-02-22 15:48   ` Dan Williams [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=1172159310.5114.2.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=jeff@garzik.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=simrw@sim-basis.de \
    /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