All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rohit Chavan <roheetchavan@gmail.com>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Rohit Chavan <roheetchavan@gmail.com>
Subject: [PATCH] nvmet: Fix warnings given by checkpatch
Date: Wed, 18 Sep 2024 13:41:34 +0530	[thread overview]
Message-ID: <20240918081134.908075-1-roheetchavan@gmail.com> (raw)

This patch addresses below issues produced by checkpatch script.

ERROR: space required before the open brace '{'
drivers/nvme/target/debugfs.h:25

WARNING: please, no spaces at the start of a line
drivers/nvme/target/debugfs.h:35

Signed-off-by: Rohit Chavan <roheetchavan@gmail.com>
---
 drivers/nvme/target/debugfs.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/nvme/target/debugfs.h b/drivers/nvme/target/debugfs.h
index cfb8bbf6a297..166de8c7fc49 100644
--- a/drivers/nvme/target/debugfs.h
+++ b/drivers/nvme/target/debugfs.h
@@ -22,7 +22,7 @@ static inline int nvmet_debugfs_subsys_setup(struct nvmet_subsys *subsys)
 {
 	return 0;
 }
-static inline void nvmet_debugfs_subsys_free(struct nvmet_subsys *subsys){}
+static inline void nvmet_debugfs_subsys_free(struct nvmet_subsys *subsys) {}
 
 static inline int nvmet_debugfs_ctrl_setup(struct nvmet_ctrl *ctrl)
 {
@@ -32,7 +32,7 @@ static inline void nvmet_debugfs_ctrl_free(struct nvmet_ctrl *ctrl) {}
 
 static inline int __init nvmet_init_debugfs(void)
 {
-    return 0;
+        return 0;
 }
 
 static inline void nvmet_exit_debugfs(void) {}
-- 
2.34.1



             reply	other threads:[~2024-09-18  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  8:11 Rohit Chavan [this message]
2024-09-18 12:03 ` [PATCH] nvmet: Fix warnings given by checkpatch Christoph Hellwig

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=20240918081134.908075-1-roheetchavan@gmail.com \
    --to=roheetchavan@gmail.com \
    --cc=hch@lst.de \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.