From: David Miller <davem@davemloft.net>
To: johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2016-07-13
Date: Wed, 13 Jul 2016 16:06:02 -0700 (PDT) [thread overview]
Message-ID: <20160713.160602.1965210574276689269.davem@davemloft.net> (raw)
In-Reply-To: <20160713082540.GA3719@t440s.lan>
From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Wed, 13 Jul 2016 11:25:40 +0300
> Here's our main bluetooth-next pull request for the 4.8 kernel:
>
> - Fixes and cleanups in 802.15.4 and 6LoWPAN code
> - Fix out of bounds issue in btmrvl driver
> - Fixes to Bluetooth socket recvmsg return values
> - Use crypto_cipher_encrypt_one() instead of crypto_skcipher
> - Cleanup of Bluetooth connection sysfs interface
> - New Authentication failure reson code for Disconnected mgmt event
> - New USB IDs for Atheros, Qualcomm and Intel Bluetooth controllers
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thanks Johan.
prev parent reply other threads:[~2016-07-13 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 8:25 pull request: bluetooth-next 2016-07-13 Johan Hedberg
2016-07-13 23:06 ` 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=20160713.160602.1965210574276689269.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).