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 2012-08-15
Date: Wed, 15 Aug 2012 15:52:06 -0700 (PDT) [thread overview]
Message-ID: <20120815.155206.172710419448408328.davem@davemloft.net> (raw)
In-Reply-To: <20120815185409.GA2137-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Date: Wed, 15 Aug 2012 14:54:10 -0400
> This is a batch of updates intended for 3.7. The ath9k, mwifiex,
> and b43 drivers get the bulk of the commits this time, with a handful
> of other driver bits thrown-in. It is mostly just minor fixes and
> cleanups, etc.
>
> Also included is a Bluetooth pull, with a lot of refactoring.
> Gustavo says:
>
> "These are the changes I queued for 3.7. There are a many
> small fixes/improvements by Andre Guedes. A l2cap channel
> refcounting refactor by Jaganath. Bluetooth sockets now
> appears in /proc/net, by Masatake Yamato and Sachin Kamat
> changes ours drivers to use devm_kzalloc()."
>
> Please let me know if there are problems!
Pulled, thanks John.
--
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:[~2012-08-15 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 18:54 pull request: wireless-next 2012-08-15 John W. Linville
[not found] ` <20120815185409.GA2137-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2012-08-15 22:52 ` 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=20120815.155206.172710419448408328.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).