From: kernel test robot <lkp@intel.com>
To: Haren Myneni <haren@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: oe-kbuild-all@lists.linux.dev, mpe@ellerman.id.au,
npiggin@gmail.com, tyreld@linux.ibm.com, brking@linux.ibm.com,
hbabu@us.ibm.com, haren@linux.ibm.com
Subject: Re: [PATCH v2 1/2] powerpc/pseries/dlpar: Remove device tree node for DLPAR IO remove
Date: Sun, 18 Aug 2024 22:07:46 +0800 [thread overview]
Message-ID: <202408182142.wuIKqYae-lkp@intel.com> (raw)
In-Reply-To: <20240817035401.125833-1-haren@linux.ibm.com>
Hi Haren,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes linus/master v6.11-rc3 next-20240816]
[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/Haren-Myneni/powerpc-pseries-dlpar-Add-device-tree-nodes-for-DLPAR-IO-add/20240817-115833
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link: https://lore.kernel.org/r/20240817035401.125833-1-haren%40linux.ibm.com
patch subject: [PATCH v2 1/2] powerpc/pseries/dlpar: Remove device tree node for DLPAR IO remove
config: powerpc64-randconfig-r121-20240818 (https://download.01.org/0day-ci/archive/20240818/202408182142.wuIKqYae-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 26670e7fa4f032a019d23d56c6a02926e854e8af)
reproduce: (https://download.01.org/0day-ci/archive/20240818/202408182142.wuIKqYae-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/202408182142.wuIKqYae-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/powerpc/platforms/pseries/dlpar.c:398:53: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] drc_index @@ got restricted __be32 [usertype] drc_index @@
arch/powerpc/platforms/pseries/dlpar.c:398:53: sparse: expected unsigned int [usertype] drc_index
arch/powerpc/platforms/pseries/dlpar.c:398:53: sparse: got restricted __be32 [usertype] drc_index
arch/powerpc/platforms/pseries/dlpar.c:418:43: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] drc_count @@ got unsigned int [usertype] @@
arch/powerpc/platforms/pseries/dlpar.c:418:43: sparse: expected restricted __be32 [usertype] drc_count
arch/powerpc/platforms/pseries/dlpar.c:418:43: sparse: got unsigned int [usertype]
arch/powerpc/platforms/pseries/dlpar.c:422:43: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] drc_index @@ got unsigned int [usertype] @@
arch/powerpc/platforms/pseries/dlpar.c:422:43: sparse: expected restricted __be32 [usertype] drc_index
arch/powerpc/platforms/pseries/dlpar.c:422:43: sparse: got unsigned int [usertype]
arch/powerpc/platforms/pseries/dlpar.c:426:42: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] count @@ got unsigned int [usertype] @@
arch/powerpc/platforms/pseries/dlpar.c:426:42: sparse: expected restricted __be32 [usertype] count
arch/powerpc/platforms/pseries/dlpar.c:426:42: sparse: got unsigned int [usertype]
arch/powerpc/platforms/pseries/dlpar.c:428:42: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] index @@ got unsigned int [usertype] @@
arch/powerpc/platforms/pseries/dlpar.c:428:42: sparse: expected restricted __be32 [usertype] index
arch/powerpc/platforms/pseries/dlpar.c:428:42: sparse: got unsigned int [usertype]
vim +398 arch/powerpc/platforms/pseries/dlpar.c
386
387 static int dlpar_hp_dt(struct pseries_hp_errorlog *phpe)
388 {
389 int rc;
390
391 if (phpe->id_type != PSERIES_HP_ELOG_ID_DRC_INDEX)
392 return -EINVAL;
393
394 lock_device_hotplug();
395
396 switch (phpe->action) {
397 case PSERIES_HP_ELOG_ACTION_REMOVE:
> 398 rc = dlpar_hp_dt_remove(phpe->_drc_u.drc_index);
399 break;
400 default:
401 pr_err("Invalid action (%d) specified\n", phpe->action);
402 rc = -EINVAL;
403 break;
404 }
405
406 unlock_device_hotplug();
407
408 return rc;
409 }
410
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-08-18 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 3:54 [PATCH v2 1/2] powerpc/pseries/dlpar: Remove device tree node for DLPAR IO remove Haren Myneni
2024-08-17 3:54 ` [PATCH v2 2/2] powerpc/pseries/dlpar: Add device tree nodes for DLPAR IO add Haren Myneni
2024-08-18 15:39 ` kernel test robot
2024-08-18 14:07 ` 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=202408182142.wuIKqYae-lkp@intel.com \
--to=lkp@intel.com \
--cc=brking@linux.ibm.com \
--cc=haren@linux.ibm.com \
--cc=hbabu@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tyreld@linux.ibm.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).