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 2010-02-12
Date: Sun, 14 Feb 2010 11:56:52 -0800 (PST) [thread overview]
Message-ID: <20100214.115652.147969784.davem@davemloft.net> (raw)
In-Reply-To: <20100212214550.GB16783@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 12 Feb 2010 16:45:50 -0500
> Here are a couple of stragglers for 2.6.33. One purports to fix a
> crash, the other avoids processing of uninitialized data when using
> devices with rate control in hardware.
>
> The latter patch will cause a merge issue in linux-next. I'll be happy
> to resolve that in wireless-next-2.6 once this merge request is
> resolved.
Pulled, thanks John.
prev parent reply other threads:[~2010-02-14 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 21:45 pull request: wireless-2.6 2010-02-12 John W. Linville
2010-02-14 19:56 ` 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=20100214.115652.147969784.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).