From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC leds + net-next v2 1/1] net: phy: marvell: add support for PHY LEDs via LED class
Date: Fri, 24 Jul 2020 10:24:53 +0800 [thread overview]
Message-ID: <202007241021.BEFfTfvg%lkp@intel.com> (raw)
In-Reply-To: <20200723181319.15988-2-marek.behun@nic.cz>
[-- Attachment #1: Type: text/plain, Size: 3206 bytes --]
Hi "Marek,
[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/Marek-Beh-n/Add-support-for-LEDs-on-Marvell-PHYs/20200724-021441
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 7fc3b978a8971305d456b32d3f2ac13191f5a0d7
config: sparc-allyesconfig (attached as .config)
compiler: sparc64-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
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sparc
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/marvell.c:920:3: error: 'struct led_trigger' has no member named 'trigger_type'
920 | .trigger_type = &marvell_led_trigger_type,
| ^~~~~~~~~~~~
>> drivers/net/phy/marvell.c:920:18: warning: initialization of 'int' from 'struct led_hw_trigger_type *' makes integer from pointer without a cast [-Wint-conversion]
920 | .trigger_type = &marvell_led_trigger_type,
| ^
drivers/net/phy/marvell.c:920:18: note: (near initialization for 'marvell_hw_led_trigger.leddev_list_lock.raw_lock.<anonymous>.cnts.counter')
drivers/net/phy/marvell.c:920:18: error: initializer element is not computable at load time
drivers/net/phy/marvell.c:920:18: note: (near initialization for 'marvell_hw_led_trigger.leddev_list_lock.raw_lock.<anonymous>.cnts.counter')
drivers/net/phy/marvell.c:916:52: warning: missing braces around initializer [-Wmissing-braces]
916 | static struct led_trigger marvell_hw_led_trigger = {
| ^
......
920 | .trigger_type = &marvell_led_trigger_type,
| {{{{ }}}}
drivers/net/phy/marvell.c: In function 'marvell_register_led':
drivers/net/phy/marvell.c:976:12: error: 'struct led_classdev' has no member named 'trigger_type'; did you mean 'trigger_lock'?
976 | led->cdev.trigger_type = &marvell_led_trigger_type;
| ^~~~~~~~~~~~
| trigger_lock
drivers/net/phy/marvell.c: At top level:
drivers/net/phy/marvell.c:688:35: error: storage size of 'marvell_led_trigger_type' isn't known
688 | static struct led_hw_trigger_type marvell_led_trigger_type;
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +920 drivers/net/phy/marvell.c
915
916 static struct led_trigger marvell_hw_led_trigger = {
917 .name = "hw-control",
918 .activate = marvell_led_trigger_activate,
919 .deactivate = marvell_led_trigger_deactivate,
> 920 .trigger_type = &marvell_led_trigger_type,
921 .groups = marvell_led_trig_groups,
922 };
923
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 66261 bytes --]
next prev parent reply other threads:[~2020-07-24 2:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 18:13 [PATCH RFC leds + net-next v2 0/1] Add support for LEDs on Marvell PHYs Marek Behún
2020-07-23 18:13 ` [PATCH RFC leds + net-next v2 1/1] net: phy: marvell: add support for PHY LEDs via LED class Marek Behún
2020-07-23 21:35 ` Andrew Lunn
2020-07-23 21:44 ` Pavel Machek
2020-07-23 21:46 ` Marek Behun
2020-07-23 22:53 ` Marek Behun
2020-07-24 10:24 ` Pavel Machek
2020-07-24 13:11 ` Andrew Lunn
2020-07-25 9:41 ` Pavel Machek
2020-07-24 2:24 ` kernel test robot [this message]
2020-07-24 2:52 ` kernel test robot
2020-07-24 10:29 ` [PATCH RFC leds + net-next v2 0/1] Add support for LEDs on Marvell PHYs Pavel Machek
2020-07-24 13:12 ` Marek Behún
2020-07-24 13:18 ` Marek Behún
2020-07-24 22:38 ` Pavel Machek
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=202007241021.BEFfTfvg%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.