linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 3/4] Bluetooth: Fix using system-global workqueue when not necessary
Date: Fri, 18 Jan 2013 03:07:25 -0200	[thread overview]
Message-ID: <20130118050725.GA13059@joana> (raw)
In-Reply-To: <1358195633-29303-4-git-send-email-johan.hedberg@gmail.com>

Hi Johan,

* Johan Hedberg <johan.hedberg@gmail.com> [2013-01-14 22:33:52 +0200]:

> From: Johan Hedberg <johan.hedberg@intel.com>
> 
> There's a per-HCI device workqueue (hdev->workqueue) that should be used
> for general per-HCI device work (except hdev->req_workqueue that's for
> hci_request() related work). This patch fixes places using the
> system-global work queue and makes them use the hdev->workqueue instead.
> 
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
>  net/bluetooth/hci_core.c |    4 ++--
>  net/bluetooth/mgmt.c     |    3 ++-
>  2 files changed, 4 insertions(+), 3 deletions(-)

Patches 1 to 3 have been applied to bluetooth-next. Thanks.

	Gustavo

  parent reply	other threads:[~2013-01-18  5:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 20:33 [PATCH 0/4] Bluetooth: Fix workqueue related issues Johan Hedberg
2013-01-14 20:33 ` [PATCH 1/4] Bluetooth: Add a new workqueue for hci_request operations Johan Hedberg
2013-01-14 20:42   ` Marcel Holtmann
2013-01-14 20:33 ` [PATCH 2/4] Bluetooth: Use req_workqueue " Johan Hedberg
2013-01-14 20:43   ` Marcel Holtmann
2013-01-14 20:33 ` [PATCH 3/4] Bluetooth: Fix using system-global workqueue when not necessary Johan Hedberg
2013-01-14 20:44   ` Marcel Holtmann
2013-01-18  5:07   ` Gustavo Padovan [this message]
2013-01-14 20:33 ` [PATCH 4/4] Bluetooth: Fix write_scan_enable when HCI_AUTO_OFF is set Johan Hedberg
2013-01-15  1:06   ` Anderson Lizardo
2013-01-16  0:36 ` [PATCH 0/4] Bluetooth: Fix workqueue related issues Mat Martineau

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=20130118050725.GA13059@joana \
    --to=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.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;
as well as URLs for NNTP newsgroup(s).