From: David Miller <davem@davemloft.net>
To: padovan@profusion.mobi
Cc: gustavo@padovan.org, johan.hedberg@gmail.com,
marcel@holtmann.org, linville@tuxdriver.com,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2012-03-08
Date: Wed, 07 Mar 2012 22:57:52 -0800 (PST) [thread overview]
Message-ID: <20120307.225752.1535997011608677011.davem@davemloft.net> (raw)
In-Reply-To: <20120308054431.GE3998@joana>
From: Gustavo Padovan <padovan@profusion.mobi>
Date: Thu, 8 Mar 2012 02:44:31 -0300
> Hi Dave,
>
> Here goes another try to merge the bluetooth-next changes. I looked to the
> whole diff of the last pull request and fixed all the style issues you
> reported in last pull request attempt. The diff is very big, so I may have
> missed some places, but we are, from your coding style point of view, in a
> much better state than before.
>
> Please take a look on it and pull if you find the code suitable, otherwise
> tell me what's wrong and how we should fix it since your coding style rules
> are not written in CodingStyle.
>
> About the patches:
> - almost half of the patches is in the new Bluetooth Management interface, it
> finally reached a stable state regarding its API and we now enable it by
> default.
> - lots of Bluetooth LE patches. This implementation is still unstable but
> disabled by default.
> - some L2CAP layer refactoring to make our core code more generic and
> reusable.
> - New HCI monitor interface to monitor Bluetooth flow.
> - Lot of fixes and clean ups all over the Bluetooth subsystem.
Pulled, thanks a lot.
next prev parent reply other threads:[~2012-03-08 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 5:44 pull request: bluetooth-next 2012-03-08 Gustavo Padovan
2012-03-08 6:57 ` David Miller [this message]
2012-03-08 8:22 ` Current bluetooth tree: Was: pull request 2012-03-08 Andrei Emeltchenko
2012-03-08 17:38 ` Mat Martineau
2012-03-08 18:20 ` Gustavo Padovan
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=20120307.225752.1535997011608677011.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).