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 12/36] drivers/irqchip/irq-gic-v3-its.c:2172:9: error: implicit declaration of function 'gits_read_vpropbaser'; did you mean 'gicr_read_vpropbaser'?
Date: Wed, 18 Sep 2019 21:00:27 +0800 [thread overview]
Message-ID: <201909182123.6lWOwV9L%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gic-v4.1-devel
head: 9da741398299fcfba5e250ee337754b7c0e10cdd
commit: c65d1f89c69acba491e723d72ddb09e4fb9721b8 [12/36] irqchip/gic-v4.1: Revamp VPENDBASER table allocation
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 c65d1f89c69acba491e723d72ddb09e4fb9721b8
# 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:2172: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
cc1: some warnings being treated as errors
vim +2172 drivers/irqchip/irq-gic-v3-its.c
2144
2145 static u64 inherit_vpe_l1_table_from_rd(cpumask_t **mask)
2146 {
2147 u32 aff;
2148 u64 val;
2149 int cpu;
2150
2151 val = gic_read_typer(gic_data_rdist_rd_base() + GICR_TYPER);
2152 aff = compute_common_aff(val);
2153
2154 for_each_possible_cpu(cpu) {
2155 void __iomem *base = gic_data_rdist_cpu(cpu)->rd_base;
2156 u32 tmp;
2157
2158 if (!base || cpu == smp_processor_id())
2159 continue;
2160
2161 val = gic_read_typer(base + GICR_TYPER);
2162 tmp = compute_common_aff(val);
2163 if (tmp != aff)
2164 continue;
2165
2166 /*
2167 * At this point, we have a victim. This particular CPU
2168 * has already booted, and has an affinity that matches
2169 * ours wrt CommonLPIAff. Let's use its own VPROPBASER.
2170 * Make sure we don't write the Z bit in that case.
2171 */
> 2172 val = gits_read_vpropbaser(base + SZ_128K + GICR_VPROPBASER);
2173 val &= ~GICR_VPROPBASER_4_1_Z;
2174
2175 *mask = gic_data_rdist_cpu(cpu)->vpe_table_mask;
2176
2177 return val;
2178 }
2179
2180 return 0;
2181 }
2182
---
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: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=201909182123.6lWOwV9L%lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=kbuild-all@01$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=maz@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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