[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <95d721d1-2ccc-321c-f688-15e5bb53c30b@redhat.com>
Date: Tue, 9 Jul 2019 15:06:49 -0400
From: Laura Abbott <labbott@...hat.com>
To: Arnd Bergmann <arnd@...db.de>, Will Deacon <will.deacon@....com>
Cc: Mark Rutland <mark.rutland@....com>,
Peter Maydell <peter.maydell@...aro.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Marc Zyngier <marc.zyngier@....com>,
Catalin Marinas <catalin.marinas@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Julien Grall <julien.grall@....com>,
Alan Hayward <alan.hayward@....com>,
Andrew Murray <andrew.murray@....com>,
Alex Bennée <alex.bennee@...aro.org>,
Dave Martin <Dave.Martin@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64/sve: fix genksyms generation
On 6/18/19 10:15 AM, Arnd Bergmann wrote:
> On Tue, Jun 18, 2019 at 2:03 PM Will Deacon <will.deacon@....com> wrote:
>>
>> From 6e004b8824d4eb6a4e61cd794fbc3a761b50135b Mon Sep 17 00:00:00 2001
>> From: Will Deacon <will.deacon@....com>
>> Date: Tue, 18 Jun 2019 12:56:49 +0100
>> Subject: [PATCH] genksyms: Teach parse about __uint128_t built-in type
>>
>> __uint128_t crops up in a few files that export symbols to modules, so
>> teach genksyms about it so that we don't end up skipping the CRC
>> generation for some symbols due to the parser failing to spot them:
>>
>> | WARNING: EXPORT symbol "kernel_neon_begin" [vmlinux] version
>> | generation failed, symbol will not be versioned.
>> | ld: arch/arm64/kernel/fpsimd.o: relocation R_AARCH64_ABS32 against
>> | `__crc_kernel_neon_begin' can not be used when making a shared
>> | object
>> | ld: arch/arm64/kernel/fpsimd.o:(.data+0x0): dangerous relocation:
>> | unsupported relocation
>>
>> Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>
>> Reported-by: Arnd Bergmann <arnd@...db.de>
>> Signed-off-by: Will Deacon <will.deacon@....com>
>
> Looks good to me,
>
> Acked-by: Arnd Bergmann <arnd@...db.de>
>
> I've added this to my randconfig build setup, replacing my earlier
> patch, and will let you know if any problems with it remain.
>
> Arnd
>
I just hit this on 5ad18b2e60b75c7297a998dea702451d33a052ed on Linus'
branch. The fix works for me (feel free to add Tested-by). Is this
already queued up for Linus?
Thanks,
Laura
Powered by blists - more mailing lists