nvme: fix typo error in nvme target

Fix two spelling mistakes.

Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>

diff --git a/drivers/nvme/target/admin-cmd.c b/drivers/nvme/target/admin-cmd.c
index 3e378153a78174a10d3dc9bb6e17b5074faf146b..3da31bb1183eb73f574285981069d31e9fa01699 100644 (file)
--- a/drivers/nvme/target/admin-cmd.c
+++ b/drivers/nvme/target/admin-cmd.c
@@ -708,7 +708,7 @@ static void nvmet_execute_identify_ctrl(struct nvmet_req *req)
 
        /*
         * We don't really have a practical limit on the number of abort
-        * comands.  But we don't do anything useful for abort either, so
+        * commands.  But we don't do anything useful for abort either, so
         * no point in allowing more abort commands than the spec requires.
         */
        id->acl = 3;

diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
index da94d1c7699eba8fe9be634a78828671183c2872..cc88e5a28c8a9d4e79df4aabdf3dd7abe79b6db7 100644 (file)
--- a/drivers/nvme/target/core.c
+++ b/drivers/nvme/target/core.c
@@ -40,7 +40,7 @@ EXPORT_SYMBOL_GPL(nvmet_wq);
  *  - the nvmet_transports array
  *
  * When updating any of those lists/structures write lock should be obtained,
- * while when reading (popolating discovery log page or checking host-subsystem
+ * while when reading (populating discovery log page or checking host-subsystem
  * link) read lock is obtained to allow concurrent reads.
  */
 DECLARE_RWSEM(nvmet_config_sem);