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-04-18
Date: Mon, 22 Apr 2013 14:57:14 -0400 [thread overview]
Message-ID: <20130422185713.GE2055@tuxdriver.com> (raw)
In-Reply-To: <20130418044836.GB29635@joana>
On Thu, Apr 18, 2013 at 01:48:36AM -0300, Gustavo Padovan wrote:
> Hi John,
>
> A set of changes intended for 3.10. The biggest changes here are from David
> Herrmann, he rewrote most of the HIDP layer making it more reliable. Marcel
> added a driver setup stage for device that need special handling on their
> early initialization. Other than that we have the usual clean ups, bugfixes
> and small improvements.
>
> Please pull or let me know of any problems! Thanks!
>
> Gustavo
>
> ---
> The following changes since commit 84bcc0c3c4b8ca4c0abed2d2dd63b7ce04f8be0e:
>
> brcmfmac: enable sk_buff queueing when credits deplete (2013-04-03 15:07:09 -0400)
>
> 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 76a388beaf92cc75b829d4a0b7d69afaaeaa4b0a:
>
> Bluetooth: Rename LE_SCANNING_* macros (2013-04-18 01:17:27 -0300)
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-04-22 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 4:48 pull request: bluetooth-next 2013-04-18 Gustavo Padovan
2013-04-22 18:57 ` 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=20130422185713.GE2055@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).