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-09-02
Date: Tue, 02 Sep 2008 17:17:06 -0700 (PDT) [thread overview]
Message-ID: <20080902.171706.135252299.davem@davemloft.net> (raw)
In-Reply-To: <20080902221511.GH3050@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Tue, 2 Sep 2008 18:15:11 -0400
> Here is this week's round of fixes. Admittedly not all of them are
> regressions with entries at bugzilla.kernel.org -- hopefully that is not
> a hard and fast requirement. :-)
>
> I think everything here is suitable for 2.6.27. Please let me know if
> there are problems.
Pulled and I'll push back out to kernel.org after my build tests complete.
prev parent reply other threads:[~2008-09-03 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 22:15 pull request: wireless-2.6 2008-09-02 John W. Linville
2008-09-02 23:07 ` Tomas Winkler
2008-09-03 0:00 ` John W. Linville
2008-09-03 0:17 ` 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=20080902.171706.135252299.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