From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Pfau Subject: Re: pull request: bluetooth-next 2015-06-18 Date: Tue, 23 Jun 2015 13:53:26 +0200 Message-ID: <558948B6.5040904@peakwork.de> References: <20150618184311.GA30772@t440s.P-661HNU-F1> <20150623.032255.394457596589182499.davem@davemloft.net> <558939EE.10206@peakwork.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , Johan Hedberg , Network Development , linux-bluetooth@vger.kernel.org To: Marcel Holtmann Return-path: Received: from mail.peakwork.de ([213.203.211.174]:45554 "EHLO mail.peakwork.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753370AbbFWLx3 (ORCPT ); Tue, 23 Jun 2015 07:53:29 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: Hi Marcel and Johan, > Hi Markus, > >>>> Here's the final bluetooth-next pull request for 4.2. >>>> >>>> - Cleanups & fixes to 802.15.4 code and related drivers >>>> - Fix btusb driver memory leak >>>> - New USB IDs for Atheros controllers >>>> - Support for BCM4324B3 UART based Broadcom controller >>>> - Fix for Bluetooth encryption key size handling >>>> - Broadcom controller initialization fixes >>>> - Support for Intel controller DDC parameters >>>> - Support for multiple Bluetooth LE advertising instances >>>> - Fix for HCI user channel cleanup path >>>> >>>> Please let me know if there are any issues pulling. Thanks. >>> Pulled, thanks Johan, >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Hi David, >> >> I didn't get any response to my issue "High CPU load when turning off BT keyboard" from 2015-06-15. >> Is it already fixed in "Fix for HCI user channel cleanup path" ? > > your issue is an userspace daemon issue and not a kernel issue. This pull request is for the kernel side of the Bluetooth subsystem. None of these have anything to do with the userspace daemon. > > I am sorry that your email has not yet been answered. However it is only 10 days old and I bet one of the maintainers for the userspace code will have a look at it soon. If not, then you can always resend it to get their attention. > > Regards > > Marcel > Thank you for your prompt reply! I'll post it like Johan suggests to the correct group! Regards, Markus