From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: bluetooth-next 2015-06-18
Date: Tue, 23 Jun 2015 03:22:55 -0700 (PDT) [thread overview]
Message-ID: <20150623.032255.394457596589182499.davem@davemloft.net> (raw)
In-Reply-To: <20150618184311.GA30772-ae+CCJ+dGXjCW7GOcxkI+ioyn5ZhHHrn@public.gmane.org>
From: Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Thu, 18 Jun 2015 21:43:11 +0300
> Here's the final bluetooth-next pull request for 4.2.
>
> - Cleanups & fixes to 802.15.4 code and related drivers
> - Fix btusb driver memory leak
> - New USB IDs for Atheros controllers
> - Support for BCM4324B3 UART based Broadcom controller
> - Fix for Bluetooth encryption key size handling
> - Broadcom controller initialization fixes
> - Support for Intel controller DDC parameters
> - Support for multiple Bluetooth LE advertising instances
> - Fix for HCI user channel cleanup path
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thanks Johan,
next prev parent reply other threads:[~2015-06-23 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 18:43 pull request: bluetooth-next 2015-06-18 Johan Hedberg
[not found] ` <20150618184311.GA30772-ae+CCJ+dGXjCW7GOcxkI+ioyn5ZhHHrn@public.gmane.org>
2015-06-23 10:22 ` David Miller [this message]
[not found] ` <20150623.032255.394457596589182499.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2015-06-23 10:50 ` Markus Pfau
[not found] ` <558939EE.10206-9kPUpXxpYhgb1SvskN2V4Q@public.gmane.org>
2015-06-23 11:14 ` Johan Hedberg
2015-06-23 11:29 ` Marcel Holtmann
2015-06-23 11:53 ` Markus Pfau
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=20150623.032255.394457596589182499.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@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).