[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20120307.225752.1535997011608677011.davem@davemloft.net>
Date: Wed, 07 Mar 2012 22:57:52 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: padovan@...fusion.mobi
Cc: gustavo@...ovan.org, johan.hedberg@...il.com, marcel@...tmann.org,
linville@...driver.com, netdev@...r.kernel.org,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: pull request: bluetooth-next 2012-03-08
From: Gustavo Padovan <padovan@...fusion.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists