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-07-31
Date: Thu, 31 Jul 2014 13:38:20 -0400 [thread overview]
Message-ID: <20140731173820.GC17560@tuxdriver.com> (raw)
In-Reply-To: <20140731074357.GA26071@t440s.lan>
On Thu, Jul 31, 2014 at 10:43:57AM +0300, Johan Hedberg wrote:
> Hi John,
>
> Here's one more (hopefully last) pull request for 3.17.
>
> We've got:
>
> - 6lowpan fixes/cleanups
> - A couple crash fixes, one for the Marvell HCI driver and another in LE SMP.
> - Fix for an incorrect connected state check
> - Fix for the bondable requirement during pairing (an issue which had
> crept in because of using "pairable" when in fact the actual meaning
> was "bondable" (these have different meanings in Bluetooth)
>
> Let me know if there are any issues. Thanks.
>
> Johan
>
> ---
> The following changes since commit 568ba389be505f505b7fbeedb9ab4ece27603fc9:
>
> brcmfmac: Fix OOB interrupt not working for BCM43362 (2014-07-29 10:32:57 -0400)
>
> 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 8500d791c458ccbbb3e2d3fa9a0320ffd5729069:
>
> Bluetooth: Fix crash in the Marvell driver initialization codepath (2014-07-31 01:07:28 +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-07-31 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 7:43 pull request: bluetooth-next 2014-07-31 Johan Hedberg
2014-07-31 17:38 ` 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=20140731173820.GC17560@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).