mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next RESEND] nvmet: Make nvmet_debugfs static
Date: Fri, 23 Aug 2024 06:41:03 +0000	[thread overview]
Message-ID: <f2ce9842-5361-423c-b281-812cb19fc2ed@nvidia.com> (raw)
In-Reply-To: <20240822071916.3547318-1-ruanjinjie@huawei.com>

On 8/22/24 00:19, Jinjie Ruan wrote:
> The sparse tool complains as follows:
>
> drivers/nvme/target/debugfs.c:16:15: warning:
> 	symbol 'nvmet_debugfs' was not declared. Should it be static?
>
> This symbol is not used outside debugfs.c, so marks it static.
>
> Signed-off-by: Jinjie Ruan<ruanjinjie@huawei.com>

I had patch written for this didn't get a chance to send [1].

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck

 From 15fc2ed4d9508d8489ce99a8794f8cbf45f2b3d2 Mon Sep 17 00:00:00 2001
From: Chaitanya Kulkarni <kch@nvidia.com>
Date: Mon, 24 Jun 2024 22:28:56 -0700
Subject: [PATCH] nvmet: mark nvmet_debugfs static

Mark struct dentry *nvmet_debugfs static in debugfs.c as it is only used
in debugfs.c to remove the following sparse warning reported by kernel
bot:-

drivers/nvme/target/debugfs.c:16:15: sparse: sparse: symbol 
'nvmet_debugfs' was not declared. Should it be static?

Reported-by: kernel test robot <lkp@intel.com>
Closes: 
https://lore.kernel.org/oe-kbuild-all/202406200501.5DrFu8Fu-lkp@intel.com/
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
  drivers/nvme/target/debugfs.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/target/debugfs.c b/drivers/nvme/target/debugfs.c
index cb2befc8619e..220c7391fc19 100644
--- a/drivers/nvme/target/debugfs.c
+++ b/drivers/nvme/target/debugfs.c
@@ -13,7 +13,7 @@
  #include "nvmet.h"
  #include "debugfs.h"

-struct dentry *nvmet_debugfs;
+static struct dentry *nvmet_debugfs;

  #define NVMET_DEBUGFS_ATTR(field) \
      static int field##_open(struct inode *inode, struct file *file) \
-- 
2.40.0



      parent reply	other threads:[~2024-08-23  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  7:19 Jinjie Ruan
2024-08-22  7:14 ` Christoph Hellwig
2024-08-23  6:41 ` Chaitanya Kulkarni [this message]

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=f2ce9842-5361-423c-b281-812cb19fc2ed@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ruanjinjie@huawei.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®