All of lore.kernel.org
 help / color / mirror / Atom feed
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-11-11
Date: Mon, 11 Nov 2013 14:05:48 -0500	[thread overview]
Message-ID: <20131111190548.GA8107@tuxdriver.com> (raw)
In-Reply-To: <20131111182738.GB5648@joana>

On Mon, Nov 11, 2013 at 04:27:38PM -0200, Gustavo Padovan wrote:
> Hi John,
> 
> A few fixes for 3.13. There is 3 fixes to the RFCOMM protocol. One crash fix to
> L2CAP. A simple fix to a bad behaviour in the SMP protocol, and last, an
> revert, that I sent in the last pull request but doesn't seem to be in your
> tree.

Are you looking in the wireless-next tree?  It seems to be there, no?

John

> 
> Please pull or let me know of any issues. Thanks!
> 
> 
> 	Gustavo
> 
> ---
> The following changes since commit 8ce9beac4661f576ea0d518b9f086bb52a171a37:
> 
>   drivers: net: wireless: b43: Fix possible NULL ptr dereference (2013-10-18 13:41:11 -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 3244d4a55c95708b0fa6fd820a9009534ed08a5f:
> 
>   Bluetooth: Fix rejecting SMP security request in slave role (2013-11-11 15:48:36 -0200)
> 
> ----------------------------------------------------------------
> Hans de Goede (1):
>       Bluetooth: revert: "Bluetooth: Add missing reset_resume dev_pm_ops"
> 
> Johan Hedberg (1):
>       Bluetooth: Fix rejecting SMP security request in slave role
> 
> Marcel Holtmann (1):
>       Bluetooth: Fix issue with RFCOMM getsockopt operation
> 
> Seung-Woo Kim (3):
>       Bluetooth: Fix RFCOMM bind fail for L2CAP sock
>       Bluetooth: Fix to set proper bdaddr_type for RFCOMM connect
>       Bluetooth: Fix crash in l2cap_chan_send after l2cap_chan_del
> 
>  drivers/bluetooth/btusb.c   | 1 -
>  net/bluetooth/l2cap_core.c  | 3 +++
>  net/bluetooth/rfcomm/core.c | 3 +++
>  net/bluetooth/rfcomm/sock.c | 6 +++++-
>  net/bluetooth/smp.c         | 3 +++
>  5 files changed, 14 insertions(+), 2 deletions(-)
> 



-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2013-11-11 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 18:27 pull request: bluetooth 2013-11-11 Gustavo Padovan
2013-11-11 19:05 ` John W. Linville [this message]
2013-11-15 15:15   ` Gustavo Padovan
2013-11-15 19:19     ` John W. Linville
2013-11-11 23:17 ` Marcel Holtmann

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=20131111190548.GA8107@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.