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-05-30
Date: Fri, 31 May 2013 12:58:28 -0400 [thread overview]
Message-ID: <20130531165827.GA2072@tuxdriver.com> (raw)
In-Reply-To: <20130530225232.GB14083@joana>
On Thu, May 30, 2013 at 07:52:32PM -0300, Gustavo Padovan wrote:
> Hi John,
>
> The following patches are important bug fixes for 3.10, plus the support for a
> new device. We do have three fixes from Johan. The first one is a fix to avoid
> LE-only devices to rely on the (inexistent) extended features data. The second
> patch fixes length checks on incoming L2CAP signalling PDUs so we can discard
> PDU whose size doesn't match the one reported in the header.
> The last one fixes the handling of power on failures, we now report proper
> errors to mgmt when hci_dev_open().
>
> Please pull or let me know of any issues! Thanks.
>
> Gustavo
>
> ---
>
> The following changes since commit f942d116b80feb3ae618a0d8ce2df6e853526d3c:
>
> brcmsmac: fix regression observed in 3.10-rc1 (2013-05-29 14:46:51 -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 0f9e216b0e12971af8a1d39c98c353c76533283b:
>
> Bluetooth: Fix mgmt handling of power on failures (2013-05-30 18:36:08 -0300)
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:[~2013-05-31 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 22:52 pull request: bluetooth 2013-05-30 Gustavo Padovan
2013-05-31 16:58 ` 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=20130531165827.GA2072@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 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.