From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC leds + net-next v3 1/2] net: phy: add API for LEDs controlled by PHY HW
Date: Sat, 25 Jul 2020 07:10:42 +0800 [thread overview]
Message-ID: <202007250716.jJ9t3QqJ%lkp@intel.com> (raw)
In-Reply-To: <20200724164603.29148-2-marek.behun@nic.cz>
[-- Attachment #1: Type: text/plain, Size: 4723 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/20200725-004937
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 1b6687e31a2df9fbdb12d25c1d1d372777bf96a8
config: nds32-allyesconfig (attached as .config)
compiler: nds32le-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=nds32
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/phy_hw_led_mode.c:79:3: error: 'struct led_trigger' has no member named 'trigger_type'
79 | .trigger_type = &phy_hw_led_trig_type,
| ^~~~~~~~~~~~
>> drivers/net/phy/phy_hw_led_mode.c:79:18: warning: excess elements in struct initializer
79 | .trigger_type = &phy_hw_led_trig_type,
| ^
drivers/net/phy/phy_hw_led_mode.c:79:18: note: (near initialization for 'phy_hw_led_trig.leddev_list_lock.raw_lock')
drivers/net/phy/phy_hw_led_mode.c:76:38: warning: missing braces around initializer [-Wmissing-braces]
76 | struct led_trigger phy_hw_led_trig = {
| ^
......
79 | .trigger_type = &phy_hw_led_trig_type,
| {{ }}
In file included from include/linux/linkage.h:7,
from include/linux/kernel.h:8,
from include/linux/list.h:9,
from include/linux/rculist.h:10,
from include/linux/pid.h:5,
from include/linux/sched.h:14,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from include/linux/leds.h:12,
from drivers/net/phy/phy_hw_led_mode.c:9:
drivers/net/phy/phy_hw_led_mode.c:74:19: error: storage size of 'phy_hw_led_trig_type' isn't known
74 | EXPORT_SYMBOL_GPL(phy_hw_led_trig_type);
| ^~~~~~~~~~~~~~~~~~~~
include/linux/export.h:98:21: note: in definition of macro '___EXPORT_SYMBOL'
98 | extern typeof(sym) sym; \
| ^~~
include/linux/export.h:155:34: note: in expansion of macro '__EXPORT_SYMBOL'
155 | #define _EXPORT_SYMBOL(sym, sec) __EXPORT_SYMBOL(sym, sec, "")
| ^~~~~~~~~~~~~~~
include/linux/export.h:159:33: note: in expansion of macro '_EXPORT_SYMBOL'
159 | #define EXPORT_SYMBOL_GPL(sym) _EXPORT_SYMBOL(sym, "_gpl")
| ^~~~~~~~~~~~~~
drivers/net/phy/phy_hw_led_mode.c:74:1: note: in expansion of macro 'EXPORT_SYMBOL_GPL'
74 | EXPORT_SYMBOL_GPL(phy_hw_led_trig_type);
| ^~~~~~~~~~~~~~~~~
drivers/net/phy/phy_hw_led_mode.c:74:19: error: storage size of 'phy_hw_led_trig_type' isn't known
74 | EXPORT_SYMBOL_GPL(phy_hw_led_trig_type);
| ^~~~~~~~~~~~~~~~~~~~
include/linux/export.h:98:21: note: in definition of macro '___EXPORT_SYMBOL'
98 | extern typeof(sym) sym; \
| ^~~
include/linux/export.h:155:34: note: in expansion of macro '__EXPORT_SYMBOL'
155 | #define _EXPORT_SYMBOL(sym, sec) __EXPORT_SYMBOL(sym, sec, "")
| ^~~~~~~~~~~~~~~
include/linux/export.h:159:33: note: in expansion of macro '_EXPORT_SYMBOL'
159 | #define EXPORT_SYMBOL_GPL(sym) _EXPORT_SYMBOL(sym, "_gpl")
| ^~~~~~~~~~~~~~
drivers/net/phy/phy_hw_led_mode.c:74:1: note: in expansion of macro 'EXPORT_SYMBOL_GPL'
74 | EXPORT_SYMBOL_GPL(phy_hw_led_trig_type);
| ^~~~~~~~~~~~~~~~~
vim +79 drivers/net/phy/phy_hw_led_mode.c
75
76 struct led_trigger phy_hw_led_trig = {
77 .name = "phydev-hw-mode",
78 .deactivate = phy_hw_led_trig_deactivate,
> 79 .trigger_type = &phy_hw_led_trig_type,
80 .groups = phy_hw_led_trig_groups,
81 };
82 EXPORT_SYMBOL_GPL(phy_hw_led_trig);
83
---
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: 57496 bytes --]
next prev parent reply other threads:[~2020-07-24 23:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 16:46 [PATCH RFC leds + net-next v3 0/2] Add support for LEDs on Marvell PHYs Marek Behún
2020-07-24 16:46 ` [PATCH RFC leds + net-next v3 1/2] net: phy: add API for LEDs controlled by PHY HW Marek Behún
2020-07-24 23:10 ` kernel test robot [this message]
2020-07-24 23:56 ` kernel test robot
2020-07-25 9:21 ` Pavel Machek
2020-07-25 9:37 ` Marek Behun
2020-07-25 16:22 ` Andrew Lunn
2020-07-24 16:46 ` [PATCH RFC leds + net-next v3 2/2] net: phy: marvell: add support for PHY LEDs via LED class Marek Behún
2020-07-25 9:23 ` Pavel Machek
2020-07-25 9:34 ` Marek Behun
2020-07-25 15:03 ` Andrew Lunn
2020-07-25 17:39 ` Marek Behun
2020-07-25 17:47 ` Andrew Lunn
2020-07-25 17:23 ` Andrew Lunn
2020-07-25 18:02 ` Marek Behun
2020-07-25 18:23 ` Andrew Lunn
2020-07-25 18:48 ` Andrew Lunn
2020-07-25 20:58 ` Marek Behun
2020-08-07 9:11 ` 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=202007250716.jJ9t3QqJ%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.