From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2012-02-24
Date: Fri, 24 Feb 2012 13:55:15 -0200 [thread overview]
Message-ID: <20120224155515.GA28741@joana> (raw)
In-Reply-To: <20120224124202.GA9908@x220>
[-- Attachment #1: Type: text/plain, Size: 1770 bytes --]
Hi John,
* Johan Hedberg <johan.hedberg@gmail.com> [2012-02-24 14:42:02 +0200]:
> Hi John,
>
> Here's a pull request for the work done in the bluetooth-next tree for
> the past month or so. It's quite a big request but the vast majority of
> changes are related to the new Bluetooth Management interface and
> doesn't touch existing functionality or interfaces. We decided to
> finally enable this interface by default (the enable_mgmt module option
> is gone) which is why we spent a good amount of time fine-tuning it so
> we have an as stable API as possible (this also contributed to the large
> amount of commits in the request).
>
> Other than the mgmt stuff there are further fixes left over from the
> move from tasklets to workqueues (related to locking, GFP_KERNEL vs.
> GFP_ATOMIC, etc). There are also fixes to Enhanced L2CAP code which
> revealed itself to be more buggy than expected at the last Bluetooth
> UnplugFest testing event.
>
> Johan
>
> ---
>
> The following changes since commit ca994a36f585432458ead9133fcfe05440edbb7b:
>
> Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless (2012-02-15 16:24:37 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jh/bluetooth-next.git for-john
>
> for you to fetch changes up to 28b8df77449faa03b573638e089a855f8d25e0ed:
>
> Bluetooth: Fix init request completion with AMP controllers (2012-02-24 14:02:21 +0200)
Acked-by: Gustavo F. Padovan <padovan@profusion.mobi>
Sorry about this big pull, for the next merge window we will be back the to
almost weekly pull requests. If this is going to cause any problem for you
tell us. Thanks for pulling!
Gustavo
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-24 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 12:42 pull request: bluetooth-next 2012-02-24 Johan Hedberg
2012-02-24 15:55 ` Gustavo Padovan [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=20120224155515.GA28741@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@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 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).