From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, gustavo@padovan.org
Subject: Re: pull request: bluetooth-next 2014-07-28
Date: Tue, 29 Jul 2014 10:26:04 -0400 [thread overview]
Message-ID: <20140729142604.GD13090@tuxdriver.com> (raw)
In-Reply-To: <20140728201610.GA29494@t440s.P-661HNU-F1>
On Mon, Jul 28, 2014 at 11:16:10PM +0300, Johan Hedberg wrote:
> Hi John,
>
> This pull request should replace the previous one that Gustavo made
> (bluetooth-next 2014-07-23).
>
> To quote Gustavo from his previous request:
>
> "Some last minute fixes for -next. We have a fix for a use after free in
> RFCOMM, another fix to an issue with ADV_DIRECT_IND and one for ADV_IND with
> auto-connection handling. Last, we added support for reading the codec and
> MWS setting for controllers that support these features."
>
> Additionally there are fixes to LE scanning, an update to conform to the 4.1
> core specification as well as fixes for tracking the page scan state. All
> of these fixes are important for 3.17.
>
> Let me know if there are any issues. Thanks.
>
> Johan
>
> ---
> The following changes since commit c2aef6e8cbebd60f79555baeb9266e220f135a44:
>
> Bluetooth: Add support for Broadcom device of Asus Z97-DELUXE motherboard (2014-07-21 15:07:08 +0300)
>
> 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 3bd2724010a51d5d15afa8065ac3c5fab3725499:
>
> Bluetooth: Fix incorrectly disabling page scan when toggling connectable (2014-07-28 20:13:32 +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-29 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 20:16 pull request: bluetooth-next 2014-07-28 Johan Hedberg
2014-07-29 14:26 ` 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=20140729142604.GD13090@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gustavo@padovan.org \
--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).