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-next 2013-01-24
Date: Wed, 30 Jan 2013 14:21:47 -0500 [thread overview]
Message-ID: <20130130192147.GC2167@tuxdriver.com> (raw)
In-Reply-To: <20130124031052.GE1632@joana>
On Thu, Jan 24, 2013 at 01:10:52AM -0200, Gustavo Padovan wrote:
> Hi John,
>
> This is my first pull request to 3.9. The biggest changes here are from Johan
> Hedberg who made a lot of fixes in the Management interface. The issues arose
> due to a new test tool we wrote and the usage of the Management interface as
> default in BlueZ 5. The rest of the patches are more clean ups and small
> fixes.
>
> Please pull! Thanks!
>
>
> Gustavo
> ---
> The following changes since commit e7f767a7d9f809c494bfffffeda2bbdbfec110b4:
>
> mwifiex: use map/unmap APIs in TX and RX to reduce memcpy (2013-01-07 15:18:30 -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 9b008c0457e583e10e62d1215bed6ab26ee54906:
>
> Bluetooth: Add support for reading LE supported states (2013-01-23 02:09:16 -0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-01-30 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 3:10 pull request: bluetooth-next 2013-01-24 Gustavo Padovan
2013-01-30 19:21 ` John W. Linville [this message]
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=20130130192147.GC2167@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 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).