netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Pull request: bluetooth-2.6 2009-05-27
Date: Wed, 27 May 2009 09:33:44 +0200	[thread overview]
Message-ID: <1243409624.20399.25.camel@localhost.localdomain> (raw)

Hi Dave,

the current 2.6.30-rc6 kernel has a lockdep issue with the work queue
handling for adding/removing connections. We are calling flush_work()
where it is not needed at all, because of the nature of the single
thread work queue. So this patch just removes these calls.

Regards

Marcel


Please pull from

    git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master

This will update the following files:

 net/bluetooth/hci_sysfs.c |    6 ------
 1 files changed, 0 insertions(+), 6 deletions(-)

through these ChangeSets:

Dave Young (1):
    Bluetooth: Remove useless flush_work() causing lockdep warnings




                 reply	other threads:[~2009-05-27  7:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1243409624.20399.25.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --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).