From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-05-28
Date: Thu, 29 May 2008 00:11:10 +0200 [thread overview]
Message-ID: <1212012670.21624.48.camel@johannes.berg> (raw)
In-Reply-To: <20080528213831.GA3133@tuxdriver.com> (sfid-20080528_235847_981601_A47BB9BE)
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
On Wed, 2008-05-28 at 17:38 -0400, John W. Linville wrote:
> David,
>
> Another round of fixes for 2.6.26 follows...
>
> Please let me know if there are problems!
What about
[PATCH] b43legacy: fix build errors when DMA or PIO are not selected
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-05-28 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 21:38 pull request: wireless-2.6 2008-05-28 John W. Linville
2008-05-28 22:11 ` Johannes Berg [this message]
2008-05-29 0:35 ` John W. Linville
2008-05-29 7:33 ` Johannes Berg
2008-05-29 8:52 ` David Miller
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=1212012670.21624.48.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--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).