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 2009-04-24
Date: Sat, 25 Apr 2009 17:45:49 -0700 (PDT) [thread overview]
Message-ID: <20090425.174549.207994669.davem@davemloft.net> (raw)
In-Reply-To: <20090424200504.GC3309@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 24 Apr 2009 16:05:05 -0400
> Here is a huge pull request for net-next-2.6, the first one this
> cycle. There is the usual huge round of driver and mac80211 updates.
> Among other things is some movement of code to enable sharing some bits
> between ath5k, ath9k, and ar9170. Also included is the beginngin of
> migration of rndis_wlan to the cfg80211 API, the first non-mac80211
> driver to do that.
>
> Please let me know if there are problems!
Since I had pulled net-2.6 into net-next-2.6, aparently after you
built this tree, there was a conflict to deal with in net/mac80211/pm.c
I hope I got it right ;-)
Pulled, thanks a lot!
prev parent reply other threads:[~2009-04-26 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 20:05 pull request: wireless-next-2.6 2009-04-24 John W. Linville
2009-04-26 0:45 ` 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=20090425.174549.207994669.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).