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: Re: [PATCH net-next] net: mdio: access c22 registers via debugfs
Date: Sun, 17 Jan 2021 06:41:28 +0800 [thread overview]
Message-ID: <202101170600.yP36sVrF-lkp@intel.com> (raw)
In-Reply-To: <20210116211916.8329-1-code@simerda.eu>
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
Hi "Pavel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Pavel-imerda/net-mdio-access-c22-registers-via-debugfs/20210117-053409
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 9ab7e76aefc97a9aa664accb59d6e8dc5e52514a
config: powerpc-adder875_defconfig (attached as .config)
compiler: powerpc-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/22d74f4896850840331d36d6867f7bc5ce728bbd
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Pavel-imerda/net-mdio-access-c22-registers-via-debugfs/20210117-053409
git checkout 22d74f4896850840331d36d6867f7bc5ce728bbd
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/net/phy/mdio-debugfs.c:170:6: warning: no previous prototype for 'mdio_debugfs_add' [-Wmissing-prototypes]
170 | void mdio_debugfs_add(struct mii_bus *bus)
| ^~~~~~~~~~~~~~~~
>> drivers/net/phy/mdio-debugfs.c:177:6: warning: no previous prototype for 'mdio_debugfs_remove' [-Wmissing-prototypes]
177 | void mdio_debugfs_remove(struct mii_bus *bus)
| ^~~~~~~~~~~~~~~~~~~
>> drivers/net/phy/mdio-debugfs.c:184:12: warning: no previous prototype for 'mdio_debugfs_init' [-Wmissing-prototypes]
184 | int __init mdio_debugfs_init(void)
| ^~~~~~~~~~~~~~~~~
>> drivers/net/phy/mdio-debugfs.c:192:13: warning: no previous prototype for 'mdio_debugfs_exit' [-Wmissing-prototypes]
192 | void __exit mdio_debugfs_exit(void)
| ^~~~~~~~~~~~~~~~~
vim +/mdio_debugfs_add +170 drivers/net/phy/mdio-debugfs.c
169
> 170 void mdio_debugfs_add(struct mii_bus *bus)
171 {
172 bus->debugfs_dentry = debugfs_create_dir(dev_name(&bus->dev), mdio_debugfs_dentry);
173 debugfs_create_file("control", 0600, bus->debugfs_dentry, bus, &mdio_debug_fops);
174 }
175 EXPORT_SYMBOL_GPL(mdio_debugfs_add);
176
> 177 void mdio_debugfs_remove(struct mii_bus *bus)
178 {
179 debugfs_remove(bus->debugfs_dentry);
180 bus->debugfs_dentry = NULL;
181 }
182 EXPORT_SYMBOL_GPL(mdio_debugfs_remove);
183
> 184 int __init mdio_debugfs_init(void)
185 {
186 mdio_debugfs_dentry = debugfs_create_dir("mdio", NULL);
187
188 return PTR_ERR_OR_ZERO(mdio_debugfs_dentry);
189 }
190 module_init(mdio_debugfs_init);
191
> 192 void __exit mdio_debugfs_exit(void)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 11832 bytes --]
next prev parent reply other threads:[~2021-01-16 22:42 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 [this message]
2021-01-16 23:20 ` kernel test robot
2021-01-16 23:20 ` [RFC PATCH] net: mdio: mdio_debug_fops can be static kernel test robot
2021-01-16 23:23 ` [PATCH net-next] net: mdio: access c22 registers via debugfs 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=202101170600.yP36sVrF-lkp@intel.com \
--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).