summaryrefslogtreecommitdiff
path: root/drivers/block/nvme-core.c
diff options
context:
space:
mode:
authorMatthew Wilcox <matthew.r.wilcox@intel.com>2013-06-24 19:56:42 +0400
committerMatthew Wilcox <matthew.r.wilcox@intel.com>2013-06-24 21:57:08 +0400
commitbc57a0f7a44cfcf3e9873f6c6b8dcecdca486b1f (patch)
treea8fbc1ebad63f840a606a9fa570b94536ff1af42 /drivers/block/nvme-core.c
parente9539f47525ecee05c9f22c3565885f3e9492c52 (diff)
downloadlinux-bc57a0f7a44cfcf3e9873f6c6b8dcecdca486b1f.tar.xz
NVMe: Remove "process_cq did something" message
I was originally intending to log the fact that the kthread had done some work since it might help us find interrupt handling problems, but that hasn't been done yet, and spamming the logs with this message is just rude. Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
Diffstat (limited to 'drivers/block/nvme-core.c')
-rw-r--r--drivers/block/nvme-core.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 88a95747494c..eb4a91f3bf41 100644
--- a/drivers/block/nvme-core.c
+++ b/drivers/block/nvme-core.c
@@ -1538,8 +1538,7 @@ static int nvme_kthread(void *data)
if (!nvmeq)
continue;
spin_lock_irq(&nvmeq->q_lock);
- if (nvme_process_cq(nvmeq))
- printk("process_cq did something\n");
+ nvme_process_cq(nvmeq);
nvme_cancel_ios(nvmeq, true);
nvme_resubmit_bios(nvmeq);
spin_unlock_irq(&nvmeq->q_lock);