From: kbuild test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm-platforms:irq/gic-v4.1-devel 28/37] drivers/irqchip/irq-gic-v3-its.c:3700:3: error: implicit declaration of function 'writeq_relaxed'; did you mean 'writew_relaxed'?
Date: Wed, 18 Sep 2019 21:34:54 +0800 [thread overview]
Message-ID: <201909182151.b8fF5qcU%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2508 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gic-v4.1-devel
head: 4d3e7d5251c6b82f804bea4fe4c6d476e18722c0
commit: 5da1b7cd29c4632a7b60472f9f85b556fd362508 [28/37] irqchip/gic-v4.1: Plumb get/set_irqchip_state SGI callbacks
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 5da1b7cd29c4632a7b60472f9f85b556fd362508
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/irqchip/irq-gic-v3-its.c: In function 'inherit_vpe_l1_table_from_rd':
drivers/irqchip/irq-gic-v3-its.c:2339:9: error: implicit declaration of function 'gits_read_vpropbaser'; did you mean 'gicr_read_vpropbaser'? [-Werror=implicit-function-declaration]
val = gits_read_vpropbaser(base + SZ_128K + GICR_VPROPBASER);
^~~~~~~~~~~~~~~~~~~~
gicr_read_vpropbaser
drivers/irqchip/irq-gic-v3-its.c: In function 'its_sgi_set_irqchip_state':
>> drivers/irqchip/irq-gic-v3-its.c:3700:3: error: implicit declaration of function 'writeq_relaxed'; did you mean 'writew_relaxed'? [-Werror=implicit-function-declaration]
writeq_relaxed(val, its->sgir_base + GITS_SGIR - SZ_128K);
^~~~~~~~~~~~~~
writew_relaxed
cc1: some warnings being treated as errors
vim +3700 drivers/irqchip/irq-gic-v3-its.c
3685
3686 static int its_sgi_set_irqchip_state(struct irq_data *d,
3687 enum irqchip_irq_state which,
3688 bool state)
3689 {
3690 if (which != IRQCHIP_STATE_PENDING)
3691 return -EINVAL;
3692
3693 if (state) {
3694 struct its_vpe *vpe = irq_data_get_irq_chip_data(d);
3695 struct its_node *its = find_4_1_its();
3696 u64 val;
3697
3698 val = FIELD_PREP(GITS_SGIR_VPEID, vpe->vpe_id);
3699 val |= FIELD_PREP(GITS_SGIR_VINTID, d->hwirq);
> 3700 writeq_relaxed(val, its->sgir_base + GITS_SGIR - SZ_128K);
3701 } else {
3702 its_configure_sgi(d, true);
3703 }
3704
3705 return 0;
3706 }
3707
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 47994 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-09-18 13:35 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=201909182151.b8fF5qcU%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@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