From: kernel test robot <lkp@intel.com>
To: Tobias Waldekranz <tobias@waldekranz.com>,
davem@davemloft.net, kuba@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, andrew@lunn.ch,
f.fainelli@gmail.com, olteanv@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: dsa: mv88e6xxx: Add LED support for 6393X
Date: Thu, 4 Jan 2024 11:16:17 +0800 [thread overview]
Message-ID: <202401041120.UXiohfGq-lkp@intel.com> (raw)
In-Reply-To: <20240103103351.1188835-3-tobias@waldekranz.com>
Hi Tobias,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Tobias-Waldekranz/net-dsa-mv88e6xxx-Add-LED-infrastructure/20240103-183726
base: net-next/main
patch link: https://lore.kernel.org/r/20240103103351.1188835-3-tobias%40waldekranz.com
patch subject: [PATCH net-next 2/2] net: dsa: mv88e6xxx: Add LED support for 6393X
config: arm64-randconfig-001-20240104 (https://download.01.org/0day-ci/archive/20240104/202401041120.UXiohfGq-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240104/202401041120.UXiohfGq-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/202401041120.UXiohfGq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/dsa/mv88e6xxx/leds.c:77:22: warning: no previous prototype for 'mv88e6393x_led_map' [-Wmissing-prototypes]
77 | const unsigned long *mv88e6393x_led_map(struct mv88e6xxx_led *led)
| ^~~~~~~~~~~~~~~~~~
drivers/net/dsa/mv88e6xxx/leds.c:398:5: warning: no previous prototype for 'mv88e6xxx_port_setup_leds' [-Wmissing-prototypes]
398 | int mv88e6xxx_port_setup_leds(struct dsa_switch *ds, int port)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/mv88e6393x_led_map +77 drivers/net/dsa/mv88e6xxx/leds.c
76
> 77 const unsigned long *mv88e6393x_led_map(struct mv88e6xxx_led *led)
78 {
79 switch (led->port) {
80 case 1:
81 case 2:
82 case 3:
83 case 4:
84 case 5:
85 case 6:
86 case 7:
87 case 8:
88 return mv88e6393x_led_map_p1_p8[led->index];
89 case 9:
90 case 10:
91 return mv88e6393x_led_map_p9_p10[led->index];
92 }
93
94 return NULL;
95 }
96
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-01-04 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 10:33 [PATCH net-next 0/2] net: dsa: mv88e6xxx: Add LED support for 6393X Tobias Waldekranz
2024-01-03 10:33 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: Add LED infrastructure Tobias Waldekranz
2024-01-03 14:09 ` Andrew Lunn
2024-01-03 14:27 ` Tobias Waldekranz
2024-01-03 23:03 ` kernel test robot
2024-01-04 0:15 ` kernel test robot
2024-01-03 10:33 ` [PATCH net-next 2/2] net: dsa: mv88e6xxx: Add LED support for 6393X Tobias Waldekranz
2024-01-04 3:16 ` kernel test robot [this message]
2024-01-04 22:01 ` 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=202401041120.UXiohfGq-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olteanv@gmail.com \
--cc=tobias@waldekranz.com \
/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).