From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2011-06-08
Date: Wed, 08 Jun 2011 15:42:06 -0700 (PDT) [thread overview]
Message-ID: <20110608.154206.659954143604324997.davem@davemloft.net> (raw)
In-Reply-To: <20110608191246.GD27028-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Date: Wed, 8 Jun 2011 15:12:47 -0400
> Dave,
>
> Here is the first big wireless pull request for the 3.1 cycle.
> As usual, this covers a lot of ground -- mostly driver updates.
>
> Some highlights include some math algorithm additions to lib/ from
> the Broadcom team, sizeable update series for rt2x00 and rtlwifi,
> the usual iwlagn and ath9k updates from the Intel and Atheros teams
> (and a few other folks), some more mwifiex updates from the Marvell
> folks, and a bunch of bcma, ssb and b43 updates from Rafał Miłecki.
...
> The following changes since commit ffbc03bc75b39c7bd412e7cc6d2185c11b0ffedd:
>
> net: add needed interrupt.h (2011-06-08 00:15:34 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git for-davem
Pulled, thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-06-08 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 19:12 pull request: wireless-next-2.6 2011-06-08 John W. Linville
[not found] ` <20110608191246.GD27028-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2011-06-08 22:42 ` 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=20110608.154206.659954143604324997.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).