Linux wireless drivers development
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-11-06
Date: Thu, 06 Nov 2008 15:59:54 -0800 (PST)	[thread overview]
Message-ID: <20081106.155954.52066801.davem@davemloft.net> (raw)
In-Reply-To: <20081106224904.GA30233@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Thu, 6 Nov 2008 17:49:04 -0500

> Here is the latest round of wireless bits intended for 2.6.28.  It
> includes a revert of an earlier fix that greatly reduced interrupts
> handled by ath5k -- testing showed that it resulted in a greater number
> of dropped associations.
> 
> Also included is an iwlwifi patch ("iwlwifi: clear scanning bits upon
> failure") that is already in -next.  It does not seem to be a strict
> regression, but since it is simple and can leave the device unable to
> scan (i.e. effectively inoperative) I think it is worth having now.
> There are also iwl3945 versions of some iwlwifi fixes as well as an
> iwl3945-specific one related to firmware errors.
> 
> Further, there is a WARN_ON fix for ath5k and another iwlwifi fix from
> me to avoid a possible sleep in softirq context.  Just for fun I've
> thrown-in a couple of zd1211rw USB ID additions as well.

Pulled, thanks a lot John.

> Please let me know if there are problems!  Any mistakes I blame on my
> recent bout of pneumonia...

Hope you feel better soon.

      reply	other threads:[~2008-11-06 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 22:49 pull request: wireless-2.6 2008-11-06 John W. Linville
2008-11-06 23:59 ` David Miller [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=20081106.155954.52066801.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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