netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Christian Marangi" <ansuelsmth@gmail.com>,
	"Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Daniel Golle" <daniel@makrotopia.org>,
	"Marek Behún" <kabel@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Li Zetao" <lizetao1@huawei.com>,
	linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH v3 1/2] leds: trigger: netdev: display only supported link speed attribute
Date: Sun, 17 Dec 2023 06:23:05 +0800	[thread overview]
Message-ID: <202312170606.NWH5SzQD-lkp@intel.com> (raw)
In-Reply-To: <20231214122041.17439-1-ansuelsmth@gmail.com>

Hi Christian,

kernel test robot noticed the following build errors:

[auto build test ERROR on lee-leds/for-leds-next]
[cannot apply to net-next/main net/main linus/master v6.7-rc5 next-20231215]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Christian-Marangi/docs-ABI-sysfs-class-led-trigger-netdev-Document-now-hidable-link_/20231214-202215
base:   https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link:    https://lore.kernel.org/r/20231214122041.17439-1-ansuelsmth%40gmail.com
patch subject: [PATCH v3 1/2] leds: trigger: netdev: display only supported link speed attribute
config: i386-randconfig-011-20231217 (https://download.01.org/0day-ci/archive/20231217/202312170606.NWH5SzQD-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312170606.NWH5SzQD-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312170606.NWH5SzQD-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: drivers/leds/trigger/ledtrig-netdev.o: in function `get_device_state':
>> drivers/leds/trigger/ledtrig-netdev.c:230: undefined reference to `phy_speeds'


vim +230 drivers/leds/trigger/ledtrig-netdev.c

   211	
   212	static void get_device_state(struct led_netdev_data *trigger_data)
   213	{
   214		struct ethtool_link_ksettings cmd;
   215		int speeds_num;
   216	
   217		trigger_data->carrier_link_up = netif_carrier_ok(trigger_data->net_dev);
   218	
   219		if (__ethtool_get_link_ksettings(trigger_data->net_dev, &cmd))
   220			return;
   221	
   222		if (trigger_data->carrier_link_up) {
   223			trigger_data->link_speed = cmd.base.speed;
   224			trigger_data->duplex = cmd.base.duplex;
   225		}
   226	
   227		/* Have a local copy of the link speed supported to not rtnl lock every time
   228		 * Modes are refreshed on any change event to handle mode changes
   229		 */
 > 230		speeds_num = phy_speeds(trigger_data->supported_link_speeds,
   231					ARRAY_SIZE(trigger_data->supported_link_speeds),
   232					cmd.link_modes.supported);
   233		trigger_data->supported_link_speeds_num = speeds_num;
   234	}
   235	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

       reply	other threads:[~2023-12-16 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231214122041.17439-1-ansuelsmth@gmail.com>
2023-12-16 22:23 ` kernel test robot [this message]
2023-12-17 12:13   ` [PATCH v3 1/2] leds: trigger: netdev: display only supported link speed attribute Christian Marangi
2023-12-16 22:34 ` 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=202312170606.NWH5SzQD-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=kabel@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=lizetao1@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pavel@ucw.cz \
    /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).