From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC V1 net-next 2/4] net: Expose available time stamping layers to user space.
Date: Tue, 04 Jan 2022 18:00:00 +0800 [thread overview]
Message-ID: <202201041705.Qy6C7VUP-lkp@intel.com> (raw)
In-Reply-To: <20220103232555.19791-3-richardcochran@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]
Hi Richard,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Richard-Cochran/Make-MAC-PHY-time-stamping-selectable/20220104-072717
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 3d694552fd8fe502e7ffd22ffa0e085bfd73b19a
config: arc-buildonly-randconfig-r001-20220104 (https://download.01.org/0day-ci/archive/20220104/202201041705.Qy6C7VUP-lkp(a)intel.com/config)
compiler: arceb-elf-gcc (GCC) 11.2.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/c7ffd872b92c08c5ffdb864da31410adb78f6a17
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Richard-Cochran/Make-MAC-PHY-time-stamping-selectable/20220104-072717
git checkout c7ffd872b92c08c5ffdb864da31410adb78f6a17
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash
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 >>):
net/core/net-sysfs.c: In function 'available_timestamping_providers_show':
>> net/core/net-sysfs.c:625:35: warning: variable 'ops' set but not used [-Wunused-but-set-variable]
625 | const struct ethtool_ops *ops;
| ^~~
net/core/net-sysfs.c: In function 'current_timestamping_provider_show':
net/core/net-sysfs.c:655:35: warning: variable 'ops' set but not used [-Wunused-but-set-variable]
655 | const struct ethtool_ops *ops;
| ^~~
vim +/ops +625 net/core/net-sysfs.c
620
621 static ssize_t available_timestamping_providers_show(struct device *dev,
622 struct device_attribute *attr,
623 char *buf)
624 {
> 625 const struct ethtool_ops *ops;
626 struct net_device *netdev;
627 struct phy_device *phydev;
628 int ret = 0;
629
630 netdev = to_net_dev(dev);
631 phydev = netdev->phydev;
632 ops = netdev->ethtool_ops;
633
634 if (!rtnl_trylock())
635 return restart_syscall();
636
637 ret += sprintf(buf, "%s\n", "mac");
638 buf += 4;
639
640 if (phy_has_tsinfo(phydev)) {
641 ret += sprintf(buf, "%s\n", "phy");
642 buf += 4;
643 }
644
645 rtnl_unlock();
646
647 return ret;
648 }
649 static DEVICE_ATTR_RO(available_timestamping_providers);
650
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-04 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 23:25 [PATCH RFC V1 net-next 2/4] net: Expose available time stamping layers to user space Richard Cochran
2022-01-03 23:51 ` Russell King (Oracle)
2022-01-04 10:00 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-08 21:19 kernel test robot
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=202201041705.Qy6C7VUP-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.