From: kernel test robot <lkp@intel.com>
To: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-arm-kernel@lists.infradead.org
Subject: [arm:zii 78/128] drivers/net/dsa/ocelot/felix_vsc9959.c:940:12: error: use of undeclared identifier 'ocelot_port'
Date: Sat, 20 Nov 2021 04:39:39 +0800 [thread overview]
Message-ID: <202111200430.kYhF0mVT-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
tree: git://git.armlinux.org.uk/~rmk/linux-arm.git zii
head: e2b78f9343e58d06b9b8561ade72f4d5aeb43e4f
commit: aa6c6c92d19e81faebd965a56b582fdc7371126c [78/128] net: dsa: ocelot: convert to phylink_generic_validate()
config: arm-randconfig-r025-20211118 (attached as .config)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
git remote add arm git://git.armlinux.org.uk/~rmk/linux-arm.git
git fetch --no-tags arm zii
git checkout aa6c6c92d19e81faebd965a56b582fdc7371126c
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/net/dsa/ocelot/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/net/dsa/ocelot/felix_vsc9959.c:940:12: error: use of undeclared identifier 'ocelot_port'
__set_bit(ocelot_port->phy_mode,
^
1 error generated.
vim +/ocelot_port +940 drivers/net/dsa/ocelot/felix_vsc9959.c
936
937 static void vsc9959_phylink_get_caps(struct ocelot *ocelot, int port,
938 struct phylink_config *config)
939 {
> 940 __set_bit(ocelot_port->phy_mode,
941 config->supported_interfaces);
942
943 config->mac_capabilities = MAC_ASYM_PAUSE | MAC_SYM_PAUSE |
944 MAC_10 | MAC_100 | MAC_1000 | MAC_2500FD;
945 }
946
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 47072 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-11-19 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202111200430.kYhF0mVT-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
/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).