From: kernel test robot <lkp@intel.com>
To: Tianyang Zhang <zhangtianyang@loongson.cn>,
chenhuacai@kernel.org, kernel@xen0n.name, corbet@lwn.net,
alexs@kernel.org, si.yanteng@linux.dev, tglx@linutronix.de,
jiaxun.yang@flygoat.com, peterz@infradead.org,
wangliupu@loongson.cn, lvjianmin@loongson.cn,
maobibo@loongson.cn, siyanteng@cqsoftware.com.cn,
gaosong@loongson.cn, yangtiezhu@loongson.cn
Cc: oe-kbuild-all@lists.linux.dev, loongarch@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tianyang Zhang <zhangtianyang@loongson.cn>
Subject: Re: [PATCH v5 2/2] irqchip/irq-loongarch-ir:Add Redirect irqchip support
Date: Sat, 11 Oct 2025 09:12:23 +0800 [thread overview]
Message-ID: <202510110810.nIsLpJni-lkp@intel.com> (raw)
In-Reply-To: <20251010022845.140234-3-zhangtianyang@loongson.cn>
Hi Tianyang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/irq/core]
[also build test WARNING on linus/master v6.17 next-20251010]
[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/Tianyang-Zhang/Docs-LoongArch-Add-Advanced-Extended-Redirect-IRQ-model-description/20251010-131542
base: tip/irq/core
patch link: https://lore.kernel.org/r/20251010022845.140234-3-zhangtianyang%40loongson.cn
patch subject: [PATCH v5 2/2] irqchip/irq-loongarch-ir:Add Redirect irqchip support
config: loongarch-randconfig-r121-20251011 (https://download.01.org/0day-ci/archive/20251011/202510110810.nIsLpJni-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251011/202510110810.nIsLpJni-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/202510110810.nIsLpJni-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/irqchip/irq-loongarch-ir.c:130:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:130:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:130:34: sparse: got void *
>> drivers/irqchip/irq-loongarch-ir.c:130:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:130:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:130:34: sparse: got void *
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: got void *
drivers/irqchip/irq-loongarch-ir.c:159:9: sparse: sparse: context imbalance in 'invalid_enqueue' - wrong count at exit
drivers/irqchip/irq-loongarch-ir.c:188:12: sparse: sparse: context imbalance in 'redirect_table_alloc' - wrong count at exit
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: got void *
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: got void *
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: got void *
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:123:34: sparse: got void *
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void [noderef] __iomem *reg_addr @@ got void * @@
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: expected void [noderef] __iomem *reg_addr
drivers/irqchip/irq-loongarch-ir.c:116:34: sparse: got void *
vim +130 drivers/irqchip/irq-loongarch-ir.c
127
128 static inline u32 redirect_read_reg32(int node, int reg)
129 {
> 130 void __iomem *reg_addr = REDIRECT_REG(reg, node);
131
132 return readl(reg_addr);
133 }
134
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-11 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 2:28 [PATCH v5 0/2] Loongarch irq-redirect support Tianyang Zhang
2025-10-10 2:28 ` [PATCH v5 1/2] Docs/LoongArch: Add Advanced Extended-Redirect IRQ model description Tianyang Zhang
2025-10-10 2:28 ` [PATCH v5 2/2] irqchip/irq-loongarch-ir:Add Redirect irqchip support Tianyang Zhang
2025-10-11 1:12 ` kernel test robot [this message]
2025-10-11 15:27 ` kernel test robot
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=202510110810.nIsLpJni-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexs@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=gaosong@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=lvjianmin@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=siyanteng@cqsoftware.com.cn \
--cc=tglx@linutronix.de \
--cc=wangliupu@loongson.cn \
--cc=yangtiezhu@loongson.cn \
--cc=zhangtianyang@loongson.cn \
/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