From: Marcel Holtmann <marcel@holtmann.org>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Process HCI events in a workqueue instead of a tasklet
Date: Tue, 10 Aug 2010 08:15:19 -0400 [thread overview]
Message-ID: <1281442519.12579.209.camel@localhost.localdomain> (raw)
In-Reply-To: <1281323213-30907-1-git-send-email-marcel@holtmann.org>
Hi everybody,
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
> include/net/bluetooth/hci_core.h | 2 +
> net/bluetooth/hci_core.c | 58 ++++++++++++++++++++++++++++++++-----
> 2 files changed, 52 insertions(+), 8 deletions(-)
so I stuffed this now into bluetooth-testing tree and would like to see
some extra testing exposure. So far this has only been tested by myself.
If there are no regression then this should make a lot of HCI and L2CAP
handling a lot simpler.
Regards
Marcel
next prev parent reply other threads:[~2010-08-10 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 3:06 [PATCH] Bluetooth: Process HCI events in a workqueue instead of a tasklet Marcel Holtmann
2010-08-10 12:15 ` Marcel Holtmann [this message]
2010-08-10 12:50 ` David Vrabel
2010-08-10 13:14 ` Marcel Holtmann
2010-08-10 14:27 ` David Vrabel
2010-08-10 21:41 ` Marcel Holtmann
2010-08-12 22:20 ` David Vrabel
2010-08-13 8:35 ` Marcel Holtmann
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=1281442519.12579.209.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@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