From: Marcel Holtmann <marcel@holtmann.org>
To: Roger Quadros <ext-roger.quadros@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC][PATCH] bluetooth: hci_sysfs: Ensure sysfs add/del is pre-empt safe
Date: Thu, 23 Apr 2009 12:42:31 +0100 [thread overview]
Message-ID: <1240486951.15894.5.camel@localhost.localdomain> (raw)
In-Reply-To: <49F05193.7070609@nokia.com>
Hi Roger,
> Subject: [PATCH] bluetooth: hci_sysfs: Ensure sysfs add/del is pre-empt safe
>
> Uses different work_struct variables for add_conn() and del_conn(). Uses
> single work queue instead of two for adding and deleting connections.
>
> It eliminates the following error on a pre-emptible kernel.
patch looks good to me. Can you just please replace the work queue name
with "bluetooth" instead if "btworkq". Looks more saner to me.
Regards
Marcel
next prev parent reply other threads:[~2009-04-23 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 11:31 [RFC][PATCH] bluetooth: hci_sysfs: Ensure sysfs add/del is pre-empt safe Roger Quadros
2009-04-23 11:42 ` Marcel Holtmann [this message]
2009-04-23 11:50 ` [PATCH v2] " Roger Quadros
2009-04-27 9:16 ` Roger Quadros
2009-04-27 9:17 ` Roger Quadros
2009-04-27 12:06 ` 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=1240486951.15894.5.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=ext-roger.quadros@nokia.com \
--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