From: kernel test robot <lkp@intel.com>
To: "Pavel Šimerda" <code@simerda.eu>, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, "Pavel Šimerda" <code@simerda.eu>
Subject: [RFC PATCH] net: mdio: mdio_debug_fops can be static
Date: Sun, 17 Jan 2021 07:20:58 +0800 [thread overview]
Message-ID: <20210116232057.GA89809@49432ef1697d> (raw)
In-Reply-To: <20210116211916.8329-1-code@simerda.eu>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
mdio-debugfs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/phy/mdio-debugfs.c b/drivers/net/phy/mdio-debugfs.c
index abed40052c20a1d..f1c9a3c604714c2 100644
--- a/drivers/net/phy/mdio-debugfs.c
+++ b/drivers/net/phy/mdio-debugfs.c
@@ -151,7 +151,7 @@ static unsigned int mdio_debug_poll(struct file *file, poll_table *wait)
return data->value == -1 ? POLLOUT : POLLIN;
}
-struct file_operations mdio_debug_fops = {
+static struct file_operations mdio_debug_fops = {
.owner = THIS_MODULE,
.open = mdio_debug_open,
.release = mdio_debug_release,
@@ -181,7 +181,7 @@ void mdio_debugfs_remove(struct mii_bus *bus)
}
EXPORT_SYMBOL_GPL(mdio_debugfs_remove);
-int __init mdio_debugfs_init(void)
+static int __init mdio_debugfs_init(void)
{
mdio_debugfs_dentry = debugfs_create_dir("mdio", NULL);
@@ -189,7 +189,7 @@ int __init mdio_debugfs_init(void)
}
module_init(mdio_debugfs_init);
-void __exit mdio_debugfs_exit(void)
+static void __exit mdio_debugfs_exit(void)
{
debugfs_remove(mdio_debugfs_dentry);
}
next prev parent reply other threads:[~2021-01-16 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 21:19 [PATCH net-next] net: mdio: access c22 registers via debugfs Pavel Šimerda
2021-01-16 22:41 ` kernel test robot
2021-01-16 23:20 ` kernel test robot
2021-01-16 23:20 ` kernel test robot [this message]
2021-01-16 23:23 ` kernel test robot
2021-01-18 23:27 ` Tobias Waldekranz
2021-01-19 0:55 ` Pavel Šimerda
2021-01-19 1:08 ` Pavel Šimerda
2021-01-19 1:11 ` Pavel Šimerda
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=20210116232057.GA89809@49432ef1697d \
--to=lkp@intel.com \
--cc=code@simerda.eu \
--cc=kbuild-all@lists.01.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).