archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <>
To: Andrew Morton <>
	Linux Memory Management List <>
Subject: [RFC PATCH linux-next] mtd: __del_mtd_partitions() can be static
Date: Wed, 11 Mar 2020 08:12:08 +0800	[thread overview]
Message-ID: <20200311001208.GA66637@f4c38e73f38a> (raw)
In-Reply-To: <>

Fixes: 57b8b2d03dbd ("mtd: implement proper partition handling")
Signed-off-by: kbuild test robot <>
 mtdpart.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/mtd/mtdpart.c b/drivers/mtd/mtdpart.c
index 93ef8fdf1634b0..3f6025684f5890 100644
--- a/drivers/mtd/mtdpart.c
+++ b/drivers/mtd/mtdpart.c
@@ -315,7 +315,7 @@ static int __mtd_del_partition(struct mtd_info *mtd)
  * This function unregisters and destroy all slave MTD objects which are
  * attached to the given MTD object, recursively.
-int __del_mtd_partitions(struct mtd_info *mtd)
+static int __del_mtd_partitions(struct mtd_info *mtd)
 	struct mtd_info *child, *next;

  reply	other threads:[~2020-03-11  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11  0:12 [linux-next:master 7020/7467] drivers/mtd/mtdpart.c:318:5: sparse: sparse: symbol '__del_mtd_partitions' was not declared. Should it be static? kbuild test robot
2020-03-11  0:12 ` kbuild test robot [this message]
2020-03-11  1:33 ` Andrew Morton
2020-03-11 13:57   ` Miquel Raynal

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200311001208.GA66637@f4c38e73f38a \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).