From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-10-31
Date: Fri, 31 Oct 2014 16:06:03 -0400 [thread overview]
Message-ID: <20141031200603.GD3768@tuxdriver.com> (raw)
In-Reply-To: <20141031182803.GA5772@t440s.P-661HNU-F1>
On Fri, Oct 31, 2014 at 08:28:03PM +0200, Johan Hedberg wrote:
> Hi John,
>
> Here's the first bluetooth-next pull request for 3.19. The vast majority
> of patches are for ieee802154 from Alexander Aring with various fixes
> and cleanups. There are also several LE/SMP fixes as well as improved
> support for handling LE devices that have lost their pairing information
> (the patches from Alfonso). Jukka provides a couple of stability fixes
> for 6lowpan and Szymon conformance fixes for RFCOMM. For the HCI drivers
> we have one new USB ID for an Acer controller as well as a reset
> handling fix for H5.
>
> Please let me know if there are any issues pulling. Thanks.
>
> Johan
>
> ---
> The following changes since commit 61ed53deb1c6a4386d8710dbbfcee8779c381931:
>
> Merge tag 'ntb-3.18' of git://github.com/jonmason/ntb (2014-10-19 12:58:22 -0700)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
>
> for you to fetch changes up to b509c02d0f31639dda90f9b7269668b86c9b25ef:
>
> Bluetooth: HCI H5 peer reset detection (2014-10-31 19:54:34 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-10-31 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 18:28 pull request: bluetooth-next 2014-10-31 Johan Hedberg
2014-10-31 20:06 ` John W. Linville [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=20141031200603.GD3768@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).