From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2013-02-01
Date: Fri, 1 Feb 2013 15:54:45 -0200 [thread overview]
Message-ID: <20130201175445.GE4733@joana> (raw)
In-Reply-To: <20130201174019.GD4733@joana>
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
Hi John,
* Gustavo Padovan <gustavo@padovan.org> [2013-02-01 15:40:19 -0200]:
> Hi John,
>
> Here goes another batch intended for 3.9, the majority of the patch here are
> from Johan who is fixing many issues in the management interface that have
> appeared lately. The rest of the patches are just small improvements, fixes
> and clean ups.
I had a brain shutdown moment and forgot to rebase against wireless-next.
SO the pull request is actually much smaller.
Please pull!
Gustavo
---
The following changes since commit c331997b6c9ad7f4b8075e6e60d3caa6e36f5938:
wil6210: fix wil_vring_init_tx status (2013-01-30 15:07:19 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next for-upstream
for you to fetch changes up to a3d09356491d637548dbe815ddb966f52ec9e53a:
Bluetooth: Refactor mgmt_pending_foreach (2013-02-01 15:50:18 -0200)
----------------------------------------------------------------
Andre Guedes (3):
Bluetooth: Reduce critical section in sco_conn_ready
Bluetooth: Remove unneeded locking
Bluetooth: Refactor mgmt_pending_foreach
Johan Hedberg (11):
Bluetooth: Store UUIDs in the same order that they were added
Bluetooth: Simplify UUIDs clearing code
Bluetooth: Keep track of UUID type upon addition
Bluetooth: Simplify UUID removal code
Bluetooth: Simplify UUID16 list generation for EIR
Bluetooth: Remove useless eir_len variable from EIR creation
Bluetooth: Refactor UUID-16 list generation into its own function
Bluetooth: Add support for 32-bit UUIDs in EIR data
Bluetooth: Add support for 128-bit UUIDs in EIR data
Bluetooth: Fix link security setting when powering on
Bluetooth: Increment Management interface revision
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 10 +-
net/bluetooth/hci_event.c | 4 -
net/bluetooth/mgmt.c | 219 +++++++++++++++++++++++++----------------
net/bluetooth/sco.c | 18 ++--
5 files changed, 150 insertions(+), 102 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-02-01 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 17:40 pull request: bluetooth-next 2013-02-01 Gustavo Padovan
2013-02-01 17:54 ` Gustavo Padovan [this message]
2013-02-01 19:22 ` John W. Linville
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=20130201175445.GE4733@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 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.