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-12-29
Date: Tue, 29 Dec 2009 19:53:36 -0800 (PST) [thread overview]
Message-ID: <20091229.195336.193710512.davem@davemloft.net> (raw)
In-Reply-To: <20091229211223.GA6104@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Tue, 29 Dec 2009 16:12:23 -0500
> Dave,
>
> Here is a somewhat large batch of fixes intended for 2.6.33. Most of
> them are simple, straightforward, and small. There is one from Johannes
> that removes a lot of code, but the code it removes is unused and the
> patch quiets a lot of build SPAM.
>
> This also includes the revert of a b43 patch that is causing some
> problems for people. It does some (apparently unnecessary) alignment
> checking that causes some allocations to fail.
>
> Please let me know if there are problems!
Pulled, thanks a lot John.
prev parent reply other threads:[~2009-12-30 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 21:12 John W. Linville
2009-12-30 3:53 ` 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=20091229.195336.193710512.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
all inboxes | Powered by JetHome®