From: Markus Pfau <markus.pfau@peakwork.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Johan Hedberg <johan.hedberg@gmail.com>,
Network Development <netdev@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2015-06-18
Date: Tue, 23 Jun 2015 13:53:26 +0200 [thread overview]
Message-ID: <558948B6.5040904@peakwork.de> (raw)
In-Reply-To: <F6D7F62D-3444-496B-BB43-0844129A4738@holtmann.org>
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
prev parent reply other threads:[~2015-06-23 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 18:43 pull request: bluetooth-next 2015-06-18 Johan Hedberg
[not found] ` <20150618184311.GA30772-ae+CCJ+dGXjCW7GOcxkI+ioyn5ZhHHrn@public.gmane.org>
2015-06-23 10:22 ` David Miller
[not found] ` <20150623.032255.394457596589182499.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2015-06-23 10:50 ` Markus Pfau
[not found] ` <558939EE.10206-9kPUpXxpYhgb1SvskN2V4Q@public.gmane.org>
2015-06-23 11:14 ` Johan Hedberg
2015-06-23 11:29 ` Marcel Holtmann
2015-06-23 11:53 ` Markus Pfau [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=558948B6.5040904@peakwork.de \
--to=markus.pfau@peakwork.de \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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).