From: Gertjan van Wingerde <gwingerde@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2010-05-25
Date: Tue, 25 May 2010 22:29:14 +0200 [thread overview]
Message-ID: <4BFC331A.9030606@gmail.com> (raw)
In-Reply-To: <20100525170401.GE31753@tuxdriver.com>
John,
On 05/25/10 19:04, John W. Linville wrote:
> Dave,
>
> Here are a number of fixes intended for 2.6.35. Included are some
> warning fixes from Randy, some smatch-identified fixes from Dan, some
> fixes for using ath9k and IBSS mode, the removal of a PCI ID that was
> optimistically added to ath9k, and a smattering of other driver fixes.
> This also includes a revert of "ath9k: Group Key fix for VAPs" which
> was reported to cause regressions due to a mac80211 change inside it
> that snuck past us... :-(
>
> Anyway, these are mostly small(ish) and obvious. Please let me know
> if there are problems!
>
> Thanks,
>
> John
>
> ---
>
> The following changes since commit acfbe96a3035639619a6533e04d88ed4ef9ccb61:
<snip>
>
> Gertjan van Wingerde (2):
> rt2x00: Fix rt2800usb TX descriptor writing.
The patch causing the breakage this patch fixes wasn't actually upstream yet. So,
applying this patch only is now introducing a bug in 2.6.35. I guess it is better
to revert this patch for 2.6.35.
Sorry for not being clearer about it when sending the patch to you.
---
Gertjan.
next prev parent reply other threads:[~2010-05-25 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 17:04 pull request: wireless-2.6 2010-05-25 John W. Linville
2010-05-25 19:23 ` Sedat Dilek
2010-05-25 19:35 ` Thomas Backlund
2010-05-25 21:08 ` reinette chatre
2010-05-25 20:15 ` David Miller
2010-05-25 20:29 ` Gertjan van Wingerde [this message]
2010-05-25 20:42 ` John W. Linville
2010-05-25 21:18 ` Gertjan van Wingerde
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=4BFC331A.9030606@gmail.com \
--to=gwingerde@gmail.com \
--cc=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).