All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Pull request: bluetooth-next-2.6 2010-07-27
Date: Tue, 27 Jul 2010 15:53:11 -0700	[thread overview]
Message-ID: <cover.1280270806.git.marcel@holtmann.org> (raw)

Hi John,

I have a few more patches for the 2.6.36 merge window. Besides the SCO
setup fix they are just cleanups anyway.

Regards

Marcel


Please pull from

    git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-next-2.6.git master

This will update the following files:

 drivers/bluetooth/hci_ath.c      |    6 +-
 drivers/bluetooth/hci_bcsp.c     |    4 +-
 drivers/bluetooth/hci_h4.c       |  107 ++------------------------------------
 drivers/bluetooth/hci_ll.c       |    4 +-
 include/net/bluetooth/hci_core.h |    2 +
 net/bluetooth/hci_conn.c         |   32 ++++++++++--
 net/bluetooth/hci_core.c         |    8 ++--
 net/bluetooth/hci_event.c        |   31 +++++------
 net/bluetooth/rfcomm/sock.c      |    2 +-
 net/bluetooth/rfcomm/tty.c       |    4 +-
 10 files changed, 63 insertions(+), 137 deletions(-)
 mode change 100755 => 100644 drivers/bluetooth/hci_ath.c

through these ChangeSets:

Dan Carpenter (1):
    Bluetooth: Fix kfree() => kfree_skb() in hci_ath.c

Gustavo F. Padovan (5):
    Bluetooth: Fix permission of hci_ath.c
    Bluetooth: Test 'count' value before enter the loop
    Bluetooth: Use hci_recv_stream_fragment() in UART driver
    Bluetooth: Add __init and __exit marks to UART drivers
    Bluetooth: Add __init and __exit marks to RFCOMM

Marcel Holtmann (1):
    Bluetooth: Defer SCO setup if mode change is pending


                 reply	other threads:[~2010-07-27 22:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cover.1280270806.git.marcel@holtmann.org \
    --to=marcel@holtmann.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 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.