summaryrefslogtreecommitdiffstats
path: root/net/nfc/hci/hcp.c
diff options
context:
space:
mode:
authorTejun Heo2012-08-23 01:22:16 +0200
committerSamuel Ortiz2012-09-25 00:17:23 +0200
commit474fee3db16c63bc440bfb93b57f72ecfc4246f0 (patch)
treef5fed7f3b40408f21fa3b9edc67d5ac0b869149f /net/nfc/hci/hcp.c
parentNFC: Remove repeated code for NULL check (diff)
downloadkernel-qcow2-linux-474fee3db16c63bc440bfb93b57f72ecfc4246f0.tar.gz
kernel-qcow2-linux-474fee3db16c63bc440bfb93b57f72ecfc4246f0.tar.xz
kernel-qcow2-linux-474fee3db16c63bc440bfb93b57f72ecfc4246f0.zip
NFC: Use system_nrt_wq instead of custom ones
NFC is using a number of custom ordered workqueues w/ WQ_MEM_RECLAIM. WQ_MEM_RECLAIM is unnecessary unless NFC is gonna be used as transport for storage device, and all use cases match one work item to one ordered workqueue - IOW, there's no actual ordering going on at all and using system_nrt_wq gives the same behavior. There's nothing to be gained by using custom workqueues. Use system_nrt_wq instead and drop all the custom ones. Signed-off-by: Tejun Heo <tj@kernel.org> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'net/nfc/hci/hcp.c')
-rw-r--r--net/nfc/hci/hcp.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/net/nfc/hci/hcp.c b/net/nfc/hci/hcp.c
index f4dad1a89740..2372b558abe9 100644
--- a/net/nfc/hci/hcp.c
+++ b/net/nfc/hci/hcp.c
@@ -108,7 +108,7 @@ int nfc_hci_hcp_message_tx(struct nfc_hci_dev *hdev, u8 pipe,
list_add_tail(&cmd->msg_l, &hdev->msg_tx_queue);
mutex_unlock(&hdev->msg_tx_mutex);
- queue_work(hdev->msg_tx_wq, &hdev->msg_tx_work);
+ queue_work(system_nrt_wq, &hdev->msg_tx_work);
return 0;