All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>, axboe@kernel.dk
Cc: kbuild-all@lists.01.org, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
Subject: [RFC PATCH] block: print_disk_stats() can be static
Date: Thu, 1 Jul 2021 02:21:14 +0800	[thread overview]
Message-ID: <20210630182114.GA45709@e2f15dc0397a> (raw)
In-Reply-To: <20210630081028.161284-1-abd.masalkhi@gmail.com>

block/genhd.c:1110:6: warning: symbol 'print_disk_stats' was not declared. Should it be static?

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 genhd.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/block/genhd.c b/block/genhd.c
index 5d393b2bc62c3..803c3448f09ae 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -1107,8 +1107,8 @@ const struct device_type disk_type = {
 
 #ifdef CONFIG_PROC_FS
 
-void print_disk_stats(struct seq_file *seqf,
-		      unsigned int inflight, struct disk_stats *stat)
+static void print_disk_stats(struct seq_file *seqf,
+			     unsigned int inflight, struct disk_stats *stat)
 {
 	seq_printf(seqf, "%lu %lu %lu %u "
 		   "%lu %lu %lu %u "

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] block: print_disk_stats() can be static
Date: Thu, 01 Jul 2021 02:21:14 +0800	[thread overview]
Message-ID: <20210630182114.GA45709@e2f15dc0397a> (raw)
In-Reply-To: <20210630081028.161284-1-abd.masalkhi@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 779 bytes --]

block/genhd.c:1110:6: warning: symbol 'print_disk_stats' was not declared. Should it be static?

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 genhd.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/block/genhd.c b/block/genhd.c
index 5d393b2bc62c3..803c3448f09ae 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -1107,8 +1107,8 @@ const struct device_type disk_type = {
 
 #ifdef CONFIG_PROC_FS
 
-void print_disk_stats(struct seq_file *seqf,
-		      unsigned int inflight, struct disk_stats *stat)
+static void print_disk_stats(struct seq_file *seqf,
+			     unsigned int inflight, struct disk_stats *stat)
 {
 	seq_printf(seqf, "%lu %lu %lu %u "
 		   "%lu %lu %lu %u "

  parent reply	other threads:[~2021-06-30 18:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  8:10 [PATCH] block: Removed a warning while compiling with a cross compiler for parisc Abd-Alrhman Masalkhi
2021-06-30 13:23 ` kernel test robot
2021-06-30 13:23   ` kernel test robot
2021-06-30 13:47 ` kernel test robot
2021-06-30 13:47   ` kernel test robot
2021-06-30 18:36   ` abd.masalkhi
2021-07-01  0:50     ` Rong Chen
2021-07-01  8:37       ` abd.masalkhi
2021-06-30 18:21 ` kernel test robot
2021-06-30 18:21   ` kernel test robot
2021-06-30 18:21 ` kernel test robot [this message]
2021-06-30 18:21   ` [RFC PATCH] block: print_disk_stats() can be static kernel test robot

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=20210630182114.GA45709@e2f15dc0397a \
    --to=lkp@intel.com \
    --cc=abd.masalkhi@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.