From: kernel test robot <lkp@intel.com>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Chen Wang <unicorn_wang@outlook.com>
Subject: [tip:irq/drivers 14/14] drivers/irqchip/irq-sg2042-msi.c:101:40: sparse: sparse: incorrect type in argument 2 (different address spaces)
Date: Mon, 21 Apr 2025 13:00:29 +0800 [thread overview]
Message-ID: <202504211251.B3aesulq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/drivers
head: e96b93a97c90181627cef6e70a0dbc8dbdae4adc
commit: e96b93a97c90181627cef6e70a0dbc8dbdae4adc [14/14] irqchip/sg2042-msi: Add the Sophgo SG2044 MSI interrupt controller
config: arm64-randconfig-r123-20250421 (https://download.01.org/0day-ci/archive/20250421/202504211251.B3aesulq-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce: (https://download.01.org/0day-ci/archive/20250421/202504211251.B3aesulq-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/202504211251.B3aesulq-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/irqchip/irq-sg2042-msi.c:101:20: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/irqchip/irq-sg2042-msi.c:101:40: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got unsigned int [usertype] * @@
drivers/irqchip/irq-sg2042-msi.c:101:40: sparse: expected void volatile [noderef] __iomem *addr
drivers/irqchip/irq-sg2042-msi.c:101:40: sparse: got unsigned int [usertype] *
vim +101 drivers/irqchip/irq-sg2042-msi.c
96
97 static void sg2044_msi_irq_ack(struct irq_data *d)
98 {
99 struct sg204x_msi_chipdata *data = irq_data_get_irq_chip_data(d);
100
> 101 writel(0, (u32 *)data->reg_clr + d->hwirq);
102 irq_chip_ack_parent(d);
103 }
104
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-21 5:01 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=202504211251.B3aesulq-lkp@intel.com \
--to=lkp@intel.com \
--cc=inochiama@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=unicorn_wang@outlook.com \
--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 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.