Messages in this thread | | | Date | Thu, 17 Sep 2020 08:12:20 +0200 | From | Borislav Petkov <> | Subject | Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332 |
| |
Hi guys,
On Thu, Sep 17, 2020 at 09:12:18AM +0800, kernel test robot wrote: > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti > branch HEAD: 767d46ab566dd489733666efe48732d523c8c332 Documentation: Add L1D flushing Documentation > > Warning in current branch: > > arch/x86/mm/tlb.c:426:36: sparse: expected void const [noderef] __percpu *__vpp_verify > arch/x86/mm/tlb.c:426:36: sparse: got bool * > arch/x86/mm/tlb.c:426:36: sparse: sparse: incorrect type in initializer (different address spaces) > > Warning ids grouped by kconfigs: > > gcc_recent_errors > `-- i386-randconfig-s002-20200916 > |-- arch-x86-mm-tlb.c:sparse:expected-void-const-noderef-__percpu-__vpp_verify > |-- arch-x86-mm-tlb.c:sparse:got-bool > `-- arch-x86-mm-tlb.c:sparse:sparse:incorrect-type-in-initializer-(different-address-spaces)-expected-void-const-noderef-__percpu-__vpp_verify-got-bool
this is another worthless bug report:
* No .config attached
* no build command line to know how you run sparse. I'm guessing with C=1. But I should not have to guess.
Pls fix.
Thx.
-- Regards/Gruss, Boris.
https://people.kernel.org/tglx/notes-about-netiquette
| |