From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>, Damien LeMoal <damien.lemoal@wdc.com>
Cc: kbuild-all@lists.01.org, linux-ide@vger.kernel.org,
Hannes Reinecke <hare@suse.de>
Subject: [RFC PATCH] libata: ata_bus_type can be static
Date: Sun, 27 Mar 2022 02:08:05 +0800 [thread overview]
Message-ID: <20220326180805.GA126281@a969c731af34> (raw)
In-Reply-To: <20220325125624.99929-2-hare@suse.de>
drivers/ata/libata-transport.c:88:17: warning: symbol 'ata_bus_type' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
drivers/ata/libata-transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ata/libata-transport.c b/drivers/ata/libata-transport.c
index e5ed5046b299e2..b9412d1fe3e083 100644
--- a/drivers/ata/libata-transport.c
+++ b/drivers/ata/libata-transport.c
@@ -85,7 +85,7 @@ struct ata_internal {
static int ata_tdev_add(struct ata_device *dev);
static void ata_tdev_delete(struct ata_device *dev);
-struct bus_type ata_bus_type = {
+static struct bus_type ata_bus_type = {
.name = "ata",
};
next prev parent reply other threads:[~2022-03-26 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 12:56 [PATCHv4 0/2] libata: sysfs naming Hannes Reinecke
2022-03-25 12:56 ` [PATCH 1/2] libata: rework " Hannes Reinecke
2022-03-26 18:08 ` kernel test robot [this message]
2022-03-26 18:12 ` kernel test robot
2022-03-25 12:56 ` [PATCH 2/2] libata: CONFIG_ATA_SYSFS_COMPAT Hannes Reinecke
2022-03-25 16:22 ` Sergey Shtylyov
2022-03-25 16:29 ` Hannes Reinecke
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=20220326180805.GA126281@a969c731af34 \
--to=lkp@intel.com \
--cc=damien.lemoal@wdc.com \
--cc=hare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox