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 2014-12-12
Date: Mon, 15 Dec 2014 13:24:11 -0500 [thread overview]
Message-ID: <20141215182409.GF21190@tuxdriver.com> (raw)
In-Reply-To: <20141212174435.GA22678@t440s.P-661HNU-F1>
On Fri, Dec 12, 2014 at 07:44:35PM +0200, Johan Hedberg wrote:
> Hi John,
>
> These fixes are intended for 3.19, note that the tree to pull from is
> bluetooth-next (unlike the subject implies). I'd have normally done a
> pull request from bluetooth.git, but since these fixes for 3.19 is all
> we have so far I thought it's simpler if you just pull from our -next
> tree. The patches consist of:
>
> - Coccinelle warning fix
> - hci_dev_lock/unlock fixes
> - Fixes for pending mgmt command handling
> - Fixes for properly following the force_lesc_support switch
> - Fix for a Microsoft branded Broadcom adapter
> - New device id for Atheros AR3012
> - Fix for BR/EDR Secure Connections enabling
>
> Please let me know if there are any issues pulling. Thanks.
>
> Johan
>
> ---
> The following changes since commit 5a34bd5f5d8119def4feb1d2b4e3906b71059416:
>
> Bluetooth: Enable events for P-256 Public Key and DHKey commands (2014-12-05 18:17:49 +0200)
>
> 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 9845904fd489288bcf693642c1b31cc463c0b660:
>
> Bluetooth: Fix mgmt response status when removing adapter (2014-12-12 13:20:12 +0100)
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-12-15 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 17:44 pull request: bluetooth 2014-12-12 Johan Hedberg
2014-12-15 18:24 ` 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=20141215182409.GF21190@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.