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 2011-05-27
Date: Mon, 30 May 2011 13:26:16 -0700 (PDT) [thread overview]
Message-ID: <20110530.132616.262919664.davem@davemloft.net> (raw)
In-Reply-To: <20110527195008.GA5092@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 27 May 2011 15:50:08 -0400
> This is a quick batch of fixes intended for 2.6.40. They are all
> small(-ish), and several of them fix either build breakage or some
> sort of regression. At least one fixes an uninitialized variable
> that could potentially cause a crash.
>
> Please let me know if there are problems!
2.6.40, wtf is that? :-)
Just kidding, pulled, thanks!
prev parent reply other threads:[~2011-05-30 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 19:50 pull request: wireless-2.6 2011-05-27 John W. Linville
2011-05-30 20:26 ` 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=20110530.132616.262919664.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).