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-03-21
Date: Mon, 25 Mar 2013 16:40:25 -0400 [thread overview]
Message-ID: <20130325204025.GF17454@tuxdriver.com> (raw)
In-Reply-To: <20130321222408.GA8890@joana>
On Thu, Mar 21, 2013 at 07:24:08PM -0300, Gustavo Padovan wrote:
> Hi John,
>
> This is our first batch of patches for 3.10. The biggest changes of this pull
> request are from Johan Hedberg, he implemented a HCI request framework to make
> life easier when we have to send many HCI commands and a block and wait for
> all of the to finish, we were able to fix a few issues in stack with the
> introduction of this framework.
>
> Other than that Dean Jenkins did a good work cleaning the RFCOMM code, the
> refcnt infrastructure was removed and now we use NULL pointer checks to know
> when a object was freed or not. That code was buggy and now it looks a way
> better.
>
> The rest of changes are clean ups, fixes and small improvements all over the
> Bluetooth subsystem.
>
> Please pull, or let me know of any issues! Thanks.
>
> Gustavo
>
> ---
> The following changes since commit 7da060c1c01b103d181dba39bce9bd141a945f99:
>
> mwifiex: add WOWLAN support (2013-03-06 16:29:17 -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 0227c7b56959cd8f5edd20b6a47db86fa553e91a:
>
> Bluetooth: fix error return code in rfcomm_add_listener() (2013-03-20 14:17:52 -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-03-25 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 22:24 pull request: bluetooth-next 2013-03-21 Gustavo Padovan
2013-03-25 20:40 ` 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=20130325204025.GF17454@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).