From: kernel test robot <lkp@intel.com>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [Intel-wired-lan] [RFC PATCH v8 06/10] netdev: expose DPLL pin handle for netdevice
Date: Sat, 10 Jun 2023 01:41:47 +0800 [thread overview]
Message-ID: <202306100131.J58IIUTX-lkp@intel.com> (raw)
In-Reply-To: <20230609121853.3607724-7-arkadiusz.kubalewski@intel.com>
Hi Arkadiusz,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on tnguy-next-queue/dev-queue]
[also build test ERROR on tnguy-net-queue/dev-queue net-next/main net/main linus/master v6.4-rc5]
[cannot apply to next-20230609]
[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/Arkadiusz-Kubalewski/dpll-documentation-on-DPLL-subsystem-interface/20230609-202453
base: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
patch link: https://lore.kernel.org/r/20230609121853.3607724-7-arkadiusz.kubalewski%40intel.com
patch subject: [Intel-wired-lan] [RFC PATCH v8 06/10] netdev: expose DPLL pin handle for netdevice
config: x86_64-randconfig-r034-20230609 (https://download.01.org/0day-ci/archive/20230610/202306100131.J58IIUTX-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add tnguy-next-queue https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git
git fetch tnguy-next-queue dev-queue
git checkout tnguy-next-queue/dev-queue
b4 shazam https://lore.kernel.org/r/20230609121853.3607724-7-arkadiusz.kubalewski@intel.com
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash net/core/
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/202306100131.J58IIUTX-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/core/rtnetlink.c:1059:11: error: no member named 'dpll_pin' in 'struct net_device'
if (dev->dpll_pin)
~~~ ^
net/core/rtnetlink.c:1060:41: error: no member named 'dpll_pin' in 'struct net_device'
size += dpll_msg_pin_handle_size(dev->dpll_pin);
~~~ ^
net/core/rtnetlink.c:1793:11: error: no member named 'dpll_pin' in 'struct net_device'
if (dev->dpll_pin) {
~~~ ^
net/core/rtnetlink.c:1794:43: error: no member named 'dpll_pin' in 'struct net_device'
ret = dpll_msg_add_pin_handle(skb, dev->dpll_pin);
~~~ ^
4 errors generated.
vim +1059 net/core/rtnetlink.c
1054
1055 static size_t rtnl_dpll_pin_size(const struct net_device *dev)
1056 {
1057 size_t size = nla_total_size(0); /* nest IFLA_DPLL_PIN */
1058
> 1059 if (dev->dpll_pin)
1060 size += dpll_msg_pin_handle_size(dev->dpll_pin);
1061
1062 return size;
1063 }
1064
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-06-09 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230609121853.3607724-7-arkadiusz.kubalewski@intel.com>
2023-06-09 17:30 ` [Intel-wired-lan] [RFC PATCH v8 06/10] netdev: expose DPLL pin handle for netdevice kernel test robot
2023-06-09 17:41 ` kernel test robot [this message]
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=202306100131.J58IIUTX-lkp@intel.com \
--to=lkp@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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).