From: kernel test robot <lkp@intel.com>
To: Jiri Pirko <jiri@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jpirko-mlxsw:jiri_devel_devlink_locking 5/42] drivers/net/wwan/t7xx/t7xx_port_devlink.c:465:42: error: 'DEVLINK_SUPPORT_FLASH_UPDATE_COMPONENT' undeclared here (not in a function); did you mean 'DEVLINK_ATTR_FLASH_UPDATE_COMPONENT'?
Date: Sun, 21 Aug 2022 14:09:55 +0800 [thread overview]
Message-ID: <202208211443.W5A3Y2z1-lkp@intel.com> (raw)
tree: https://github.com/jpirko/linux_mlxsw jiri_devel_devlink_locking
head: e7096f2b22b32bd60568d91d12b562b3314bc8cc
commit: d8cf683bc939bf07c19efa964a98f10829e30df4 [5/42] net: devlink: extend info_get() version put to indicate a flash component
config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20220821/202208211443.W5A3Y2z1-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.1.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
# https://github.com/jpirko/linux_mlxsw/commit/d8cf683bc939bf07c19efa964a98f10829e30df4
git remote add jpirko-mlxsw https://github.com/jpirko/linux_mlxsw
git fetch --no-tags jpirko-mlxsw jiri_devel_devlink_locking
git checkout d8cf683bc939bf07c19efa964a98f10829e30df4
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/net/wwan/t7xx/t7xx_port_devlink.c:465:42: error: 'DEVLINK_SUPPORT_FLASH_UPDATE_COMPONENT' undeclared here (not in a function); did you mean 'DEVLINK_ATTR_FLASH_UPDATE_COMPONENT'?
465 | .supported_flash_update_params = DEVLINK_SUPPORT_FLASH_UPDATE_COMPONENT,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| DEVLINK_ATTR_FLASH_UPDATE_COMPONENT
vim +465 drivers/net/wwan/t7xx/t7xx_port_devlink.c
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 462
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 463 /* Call back function for devlink ops */
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 464 static const struct devlink_ops devlink_flash_ops = {
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 @465 .supported_flash_update_params = DEVLINK_SUPPORT_FLASH_UPDATE_COMPONENT,
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 466 .flash_update = t7xx_devlink_flash_update,
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 467 .reload_actions = BIT(DEVLINK_RELOAD_ACTION_DRIVER_REINIT) |
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 468 BIT(DEVLINK_RELOAD_ACTION_FW_ACTIVATE),
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 469 .reload_down = t7xx_devlink_reload_down,
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 470 .reload_up = t7xx_devlink_reload_up,
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 471 };
87dae9e70bf7be2 M Chetan Kumar 2022-08-16 472
:::::: The code at line 465 was first introduced by commit
:::::: 87dae9e70bf7be2bd8a3c561fe3ddf666eb8a7a4 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection
:::::: TO: M Chetan Kumar <m.chetan.kumar@linux.intel.com>
:::::: CC: David S. Miller <davem@davemloft.net>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-21 6:10 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=202208211443.W5A3Y2z1-lkp@intel.com \
--to=lkp@intel.com \
--cc=jiri@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®