From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: pull request: bluetooth 2013-06-23
Date: Sun, 23 Jun 2013 03:13:51 +0100 [thread overview]
Message-ID: <20130623021351.GA2327@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hi John,
A important fix to 3.10, this patch fixes an issues that was preventing the
l2cap info response command to be handled properly. Please pull. Thanks!
Gustavo
---
The following changes since commit fcb3701849957917a234a61b58ad70ed35c83eda:
brcmfmac: free primary net_device when brcmf_bus_start() fails (2013-06-13 13:24:12 -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 3f6fa3d489e127ca5a5b298eabac3ff5dbe0e112:
Bluetooth: Fix invalid length check in l2cap_information_rsp() (2013-06-23 00:24:58 +0100)
----------------------------------------------------------------
Jaganath Kanakkassery (1):
Bluetooth: Fix invalid length check in l2cap_information_rsp()
net/bluetooth/l2cap_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-06-23 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 2:13 Gustavo Padovan [this message]
2013-06-23 7:58 ` pull request: bluetooth 2013-06-23 Johan Hedberg
2013-06-23 13:01 ` Marcel Holtmann
2013-06-24 17:58 ` John W. Linville
2013-06-25 20:12 ` Pavel Machek
2013-06-25 20:49 ` Marcel Holtmann
2013-06-25 21:00 ` Gustavo Padovan
2013-06-26 11:52 ` Pavel Machek
2013-06-26 12:47 ` Gustavo Padovan
2013-07-15 12:28 ` Pavel Machek
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=20130623021351.GA2327@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).