From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2010-02-12
Date: Sun, 14 Feb 2010 17:47:11 -0800 (PST) [thread overview]
Message-ID: <20100214.174711.180120335.davem@davemloft.net> (raw)
In-Reply-To: <20100212214505.GA16783@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 12 Feb 2010 16:45:06 -0500
> Here is this weeks dump of wireless bits intended for 2.6.34. It is the
> usual variety of driver updates and fixes to problems introduced by
> updates earlier in the cycle. Also, more progress on N-phy support in
> b43 and the removal of the unused mac80211 op get_tx_stats.
>
> Please let me know if there are problems!
Pulled, thanks John.
I'm going to pull net-2.6 into net-next-2.6 and try to sort out
the wireless merge issues myself.
prev parent reply other threads:[~2010-02-15 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 21:45 pull request: wireless-next-2.6 2010-02-12 John W. Linville
2010-02-15 1:47 ` 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.174711.180120335.davem@davemloft.net \
--to=davem@davemloft.net \
--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).