From: Johan Hedberg <johan.hedberg@gmail.com>
To: Markus Pfau <markus.pfau@peakwork.de>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2015-06-18
Date: Tue, 23 Jun 2015 14:14:10 +0300 [thread overview]
Message-ID: <20150623111410.GA8703@t440s.lan> (raw)
In-Reply-To: <558939EE.10206@peakwork.de>
Hi Markus,
On Tue, Jun 23, 2015, Markus Pfau wrote:
> Am 23.06.2015 um 12:22 schrieb David Miller:
> >From: Johan Hedberg <johan.hedberg@gmail.com>
> >Date: Thu, 18 Jun 2015 21:43:11 +0300
> >
> >>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 (and fix) is user space related whereas this pull request was
for the kernel, so they are completely unrelated (we shouldn't bother
the netdev folks any further with this so please drop Dave and netdev if
you reply to this).
As for your fix, please resend it to linux-bluetooth using git
send-email so that we can continue the discussion around it there.
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Markus Pfau <markus.pfau-9kPUpXxpYhgb1SvskN2V4Q@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: bluetooth-next 2015-06-18
Date: Tue, 23 Jun 2015 14:14:10 +0300 [thread overview]
Message-ID: <20150623111410.GA8703@t440s.lan> (raw)
In-Reply-To: <558939EE.10206-9kPUpXxpYhgb1SvskN2V4Q@public.gmane.org>
Hi Markus,
On Tue, Jun 23, 2015, Markus Pfau wrote:
> Am 23.06.2015 um 12:22 schrieb David Miller:
> >From: Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >Date: Thu, 18 Jun 2015 21:43:11 +0300
> >
> >>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-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 (and fix) is user space related whereas this pull request was
for the kernel, so they are completely unrelated (we shouldn't bother
the netdev folks any further with this so please drop Dave and netdev if
you reply to this).
As for your fix, please resend it to linux-bluetooth using git
send-email so that we can continue the discussion around it there.
Johan
next prev parent reply other threads:[~2015-06-23 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 18:43 pull request: bluetooth-next 2015-06-18 Johan Hedberg
2015-06-23 10:22 ` David Miller
2015-06-23 10:22 ` David Miller
2015-06-23 10:50 ` Markus Pfau
2015-06-23 10:50 ` Markus Pfau
2015-06-23 11:14 ` Johan Hedberg [this message]
2015-06-23 11:14 ` Johan Hedberg
2015-06-23 11:29 ` Marcel Holtmann
2015-06-23 11:29 ` Marcel Holtmann
2015-06-23 11:53 ` Markus Pfau
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=20150623111410.GA8703@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=markus.pfau@peakwork.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.