From: kernel test robot <lkp@intel.com>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 19621/19841] arch/loongarch/pci/pci.c:47:10: warning: shift count >= width of type
Date: Sat, 24 Oct 2026 09:17:31 +0200 [thread overview]
Message-ID: <202610240921.rxXxjiK4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 20a33c6b6cbe7e4805dfb6cd68816937443aa148
commit: 8bb068a4a74510c3609ebb9ca2448c0c3d4fd8b6 [19621/19841] LoongArch: Use pa_to_nid()/nid_to_addrbase() rather than hard-code
config: loongarch-randconfig-r2311-20261023 (https://download.01.org/0day-ci/archive/20261024/202610240921.rxXxjiK4-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project a808f8ea7fdc61ead417bfe55e8ef5f728776aeb)
sparse: v0.6.5-rc1-1-gc4640450
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261024/202610240921.rxXxjiK4-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/202610240921.rxXxjiK4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/loongarch/pci/pci.c:47:10: warning: shift count >= width of type [-Wshift-count-overflow]
47 | return (nid_to_addrbase(node) | MCFG_EXT_PCICFG_BASE);
| ^~~~~~~~~~~~~~~~~~~~~
arch/loongarch/include/asm/numa.h:17:45: note: expanded from macro 'nid_to_addrbase'
17 | #define nid_to_addrbase(nid) (_ULCAST_(nid) << NODE_ADDRSPACE_SHIFT)
| ^ ~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +47 arch/loongarch/pci/pci.c
44
45 phys_addr_t mcfg_addr_init(int node)
46 {
> 47 return (nid_to_addrbase(node) | MCFG_EXT_PCICFG_BASE);
48 }
49
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-24 7:17 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=202610240921.rxXxjiK4-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@loongson.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.