From: David Miller <davem@davemloft.net>
To: johan.hedberg@gmail.com
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2015-02-03
Date: Wed, 04 Feb 2015 13:56:57 -0800 (PST) [thread overview]
Message-ID: <20150204.135657.922951850114728698.davem@davemloft.net> (raw)
In-Reply-To: <20150203082123.GA13130@t440s.lan>
From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Tue, 3 Feb 2015 10:21:23 +0200
> Here's what's likely the last bluetooth-next pull request for 3.20.
> Notable changes include:
>
> - xHCI workaround + a new id for the ath3k driver
> - Several new ids for the btusb driver
> - Support for new Intel Bluetooth controllers
> - Minor cleanups to ieee802154 code
> - Nested sleep warning fix in socket accept() code path
> - Fixes for Out of Band pairing handling
> - Support for LE scan restarting for HCI_QUIRK_STRICT_DUPLICATE_FILTER
> - Improvements to data we expose through debugfs
> - Proper handling of Hardware Error HCI events
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thanks Johan.
prev parent reply other threads:[~2015-02-04 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 8:21 pull request: bluetooth-next 2015-02-03 Johan Hedberg
2015-02-04 21:56 ` 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=20150204.135657.922951850114728698.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--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).