From: kernel test robot <lkp@intel.com>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: [tip:irq/drivers 15/18] drivers/irqchip/irq-loongson-pch-pic.c:451:22: error: use of undeclared identifier 'physaddr_t'; did you mean 'phys_addr_t'?
Date: Sun, 18 Jan 2026 19:22:28 +0800 [thread overview]
Message-ID: <202601181914.0ft2oolW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/drivers
head: fba6ab8010bb3e77f7a590deae9ab23b49cb051d
commit: 6e419473461bda5be6888de436d89753c1d260b3 [15/18] irqchip/loongson-pch-pic: Adjust irqchip driver for 32BIT/64BIT
config: loongarch-allnoconfig (https://download.01.org/0day-ci/archive/20260118/202601181914.0ft2oolW-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260118/202601181914.0ft2oolW-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/202601181914.0ft2oolW-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/irqchip/irq-loongson-pch-pic.c:451:22: error: use of undeclared identifier 'physaddr_t'; did you mean 'phys_addr_t'?
451 | phys_addr_t addr = (physaddr_t)acpi_pchpic->address;
| ^~~~~~~~~~
include/linux/types.h:169:13: note: 'phys_addr_t' declared here
169 | typedef u64 phys_addr_t;
| ^
1 error generated.
vim +451 drivers/irqchip/irq-loongson-pch-pic.c
448
449 int __init pch_pic_acpi_init(struct irq_domain *parent, struct acpi_madt_bio_pic *acpi_pchpic)
450 {
> 451 phys_addr_t addr = (physaddr_t)acpi_pchpic->address;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-18 11:22 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=202601181914.0ft2oolW-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=x86@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