[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5613ABE3.6060002@arm.com>
Date: Tue, 6 Oct 2015 12:09:23 +0100
From: "Suzuki K. Poulose" <Suzuki.Poulose@....com>
To: kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...org, linux-arm-kernel@...ts.infradead.org,
marc.zyngier@....com, will.deacon@....com, mark.rutland@....com,
catalin.marinas@....com, steve.capper@...aro.org,
linux-kernel@...r.kernel.org, andre.przywara@....com,
dave.martin@....com, Vladimir.Murzin@....com, james.morse@....com,
ard.biesheuvel@...aro.org, edward.nevill@...aro.org, aph@...hat.com
Subject: Re: [PATCH v2 12/22] arm64: Delay cpu feature checks
On 06/10/15 05:41, kbuild test robot wrote:
> Hi Suzuki,
>
> [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore]
>
> config: arm64-alldefconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=arm64
>
> Note: the linux-review/Suzuki-K-Poulose/arm64-Consolidate-CPU-feature-handling HEAD bfdef3a10032e84cc7ae186a058443219f110679 builds fine.
> It only hurts bisectibility.
>
> All errors (new ones prefixed by >>):
>
> arch/arm64/kernel/cpufeature.c: In function 'cpu_enable_features':
>>> arch/arm64/kernel/cpufeature.c:733:52: error: 'const struct arm64_cpu_capabilities' has no member named 'sys_reg'
> if(!cpus_have_cap(caps[i].capability) || !caps[i].sys_reg)
> ^
> arch/arm64/kernel/cpufeature.c:739:47: error: 'const struct arm64_cpu_capabilities' has no member named 'sys_reg'
> if (!feature_matches(read_cpu_sysreg(caps[i].sys_reg), &caps[i]))
> ^
That was a mistake in rebase/reordering of patches. Have fixed it internally, will include
it in the next version
Thanks @kbuild-test-robot for the report
Suzuki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists