linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	linux-bluetooth@vger.kernel.org
Subject: pull request: bluetooth-2.6 2011-06-08
Date: Wed, 8 Jun 2011 16:46:58 -0300	[thread overview]
Message-ID: <20110608194658.GD13036@joana> (raw)

Hi John,

First round of fixed for 3.0! There are here a regression fix for 1.1 and
earlier devices and a fix in the shutdown of SCO sockets.  Other 3 patches are
warning shut up. And one byte leak to userspace fix.

Please pull, thanks!


The following changes since commit 51e65257142a87fe46a1ce5c35c86c5baf012614:

  iwlegacy: fix channel switch locking (2011-06-08 14:19:05 -0400)

are available in the git repository at:
  master.kernel.org:/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git master

David Miller (2):
      Bluetooth: Do not ignore errors returned from strict_strtol()
      Bluetooth: Kill set but unused variable 'cmd' in cmtp_recv_capimsg()

Filip Palian (1):
      Bluetooth: l2cap and rfcomm: fix 1 byte infoleak to userspace.

Luiz Augusto von Dentz (1):
      Bluetooth: fix shutdown on SCO sockets

Stephen Boyd (1):
      Bluetooth: Silence DEBUG_STRICT_USER_COPY_CHECKS=y warning

Ville Tervo (1):
      Bluetooth: Do not send SET_EVENT_MASK for 1.1 and earlier devices

 drivers/bluetooth/btmrvl_debugfs.c |   12 ++++++++++++
 net/bluetooth/cmtp/capi.c          |    3 +--
 net/bluetooth/hci_event.c          |   18 ++++++++++--------
 net/bluetooth/l2cap_sock.c         |    1 +
 net/bluetooth/rfcomm/sock.c        |    4 +++-
 net/bluetooth/sco.c                |   13 ++++++++++++-
 6 files changed, 39 insertions(+), 12 deletions(-)


	Gustavo 

             reply	other threads:[~2011-06-08 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 19:46 Gustavo F. Padovan [this message]
2011-06-09 17:59 ` pull request: bluetooth-2.6 2011-06-08 John W. Linville
2011-06-09 18:34   ` Gustavo F. Padovan
2011-06-10 17:53     ` John W. Linville
2011-06-10 18:05       ` Gustavo F. 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=20110608194658.GD13036@joana \
    --to=padovan@profusion.mobi \
    --cc=linux-bluetooth@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).