From: "John W. Linville" <linville@tuxdriver.com>
To: Gustavo Padovan <gustavo@padovan.org>,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth 2013-06-13
Date: Thu, 13 Jun 2013 13:17:12 -0400 [thread overview]
Message-ID: <20130613171711.GB3246@tuxdriver.com> (raw)
In-Reply-To: <20130613112228.GB17870@joana>
On Thu, Jun 13, 2013 at 12:22:28PM +0100, Gustavo Padovan wrote:
> Hi John,
>
> A few important fixes to 3.10. The first one is a crash fix and talks by itself.
> Then we have the support for a device id, it should be fine if you want to
> remove this. Next there are two btmrvl fixes, one for a potential race
> condition that could make its main thread never stop and the other to fix the
> return code when a memory allocation fails. It was returning 0 instead of
> -ENOMEM. Last is a fix to an issue that affects at least some Thinkpad X60,
> Initialization on those laptops were failing due by unsupported cmd we were
> sending to the device. The patch fixes this by checking if the cmd is
> supported first.
>
> Please pull or let me know of any concerns you may have.
>
> Gustavo
>
> ---
> The following changes since commit d90b9e29ec5fe7a08eb7965386ebb47615306584:
>
> Merge branch 'for-john' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes (2013-06-12 14:28:21 -0400)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth master
>
> for you to fetch changes up to 0e1aba9361bf292fbdca781d419dca67d6b9911f:
>
> Bluetooth: btmrvl: fix thread stopping race (2013-06-13 11:48:38 +0100)
>
> ----------------------------------------------------------------
I applied these manually to the wireless tree:
> Anderson Lizardo (1):
> Bluetooth: Fix crash in l2cap_build_cmd() with small MTU
>
> Daniel Drake (1):
> Bluetooth: btmrvl: fix thread stopping race
>
> Johan Hedberg (1):
> Bluetooth: Fix conditions for HCI_Delete_Stored_Link_Key
These I will manually apply to wireless-next:
> Cho, Yu-Chen (1):
> Bluetooth: Add support for Mediatek Bluetooth device [0e8d:763f]
>
> Wei Yongjun (1):
> Bluetooth: btmrvl: fix error return code in btmrvl_sdio_card_to_host()
The device ID one might be OK, but it can wait for now. The error
return code patch fixes the return code for a function whose return
code isn't actually checked, so it doesn't seem to need a quick fix.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-06-13 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 11:22 pull request: bluetooth 2013-06-13 Gustavo Padovan
2013-06-13 17:17 ` John W. Linville [this message]
2013-06-13 17:48 ` Gustavo Padovan
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=20130613171711.GB3246@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).