All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Bryan Gurney <bgurney@redhat.com>
Cc: dm-devel@redhat.com, kbuild-all@01.org,
	Mike Snitzer <snitzer@redhat.com>
Subject: [RFC PATCH dm] dm: dust_rb_search() can be static
Date: Sat, 27 Apr 2019 07:12:48 +0800	[thread overview]
Message-ID: <20190426231248.GA44578@ivb42> (raw)
In-Reply-To: <201904270727.g6e3MBmi%lkp@intel.com>


Fixes: cefb8eb074c8 ("dm: add dust target")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 dm-dust.c |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/md/dm-dust.c b/drivers/md/dm-dust.c
index f5434ada..dd56284 100644
--- a/drivers/md/dm-dust.c
+++ b/drivers/md/dm-dust.c
@@ -32,7 +32,7 @@ struct dust_device {
 	bool quiet_mode:1;
 };
 
-struct badblock *dust_rb_search(struct rb_root *root, sector_t blk)
+static struct badblock *dust_rb_search(struct rb_root *root, sector_t blk)
 {
 	struct rb_node *node = root->rb_node;
 
@@ -50,7 +50,7 @@ struct badblock *dust_rb_search(struct rb_root *root, sector_t blk)
 	return NULL;
 }
 
-bool dust_rb_insert(struct rb_root *root, struct badblock *new)
+static bool dust_rb_insert(struct rb_root *root, struct badblock *new)
 {
 	struct badblock *bblk;
 	struct rb_node **link = &root->rb_node, *parent = NULL;
@@ -492,7 +492,7 @@ static struct target_type dust_target = {
 	.prepare_ioctl = dust_prepare_ioctl,
 };
 
-int __init dm_dust_init(void)
+static int __init dm_dust_init(void)
 {
 	int result = dm_register_target(&dust_target);
 
@@ -502,7 +502,7 @@ int __init dm_dust_init(void)
 	return result;
 }
 
-void __exit dm_dust_exit(void)
+static void __exit dm_dust_exit(void)
 {
 	dm_unregister_target(&dust_target);
 }

      reply	other threads:[~2019-04-26 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 23:12 [dm:dm-5.2 22/22] drivers/md/dm-dust.c:35:17: sparse: sparse: symbol 'dust_rb_search' was not declared. Should it be static? kbuild test robot
2019-04-26 23:12 ` kbuild test robot [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=20190426231248.GA44578@ivb42 \
    --to=lkp@intel.com \
    --cc=bgurney@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=snitzer@redhat.com \
    /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.