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 2009-11-11
Date: Wed, 11 Nov 2009 11:20:31 -0800 (PST) [thread overview]
Message-ID: <20091111.112031.184370997.davem@davemloft.net> (raw)
In-Reply-To: <20091111172255.GH4392@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 11 Nov 2009 12:22:55 -0500
> Here is another batch of small fixes intended for 2.6.32. Along with a
> number of simple fixes, there is also a MAINTAINERS update, some LED
> handling quirks for ath5k, a libertas beautification that is a prereq
> for a libertas fix, and an iwlwifi fix that was already sent for
> net-next-2.6 but which is needed to support an iwlwifi regression fix.
>
> My personal favorite is the ath5k mcast filtering fix. The problem
> only revealed itself when using IP autoconf w/ multicast DNS... :-)
>
> Please let me know if there are problems!
Pulled, but that libertas "coding style cleanup" really pushes
the edge of what I'm willing to take into net-2.6 right now.
And I don't want to hear anything about how it "makes the bug fix
change simpler". That absolutely doesn't apply when we're this deep
in -rc territory.
> P.S. Due to the aformentioned iwlwifi fix, this will cause -next
> conflicts for sfr. You may want to pull net-2.6 into net-next-2.6 after
> pulling this. The iwlwifi conflicts can be resolved by taking the bigger
> hunks...
Yep, I noticed this, I'll sort it out, thanks.
next prev parent reply other threads:[~2009-11-11 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 17:22 pull request: wireless-2.6 2009-11-11 John W. Linville
2009-11-11 19:20 ` David Miller [this message]
[not found] ` <20091111.112031.184370997.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-11-11 19:41 ` David Miller
2009-11-11 20:51 ` John W. Linville
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=20091111.112031.184370997.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;
as well as URLs for NNTP newsgroup(s).