[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbc2efbd-b354-7f05-7d4e-600b21fcfff6@arm.com>
Date: Thu, 26 Sep 2019 21:29:53 +0100
From: Vincenzo Frascino <vincenzo.frascino@....com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: ard.biesheuvel@...aro.org, ndesaulniers@...gle.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de, will@...nel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 0/4] arm64: vdso32: Address various issues
On 9/26/19 4:31 PM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 02:38:01PM +0100, Vincenzo Frascino wrote:
>> this patch series is meant to address the various compilation issues you
>> reported about arm64 vdso32. (This time for real I hope ;))
>>
>> Please let me know if there is still something missing.
>
> Apart from the diff I posted and some nitpicks, the series looks fine to
> me. If you post an update, I'll ack it (and a tested-by).
>
> In addition to this series I'd still prefer to have my Kconfig option to
> disable the compat vDSO if something else fails in the future (at least
> until we complete the headers clean-up). But I'm fine with a default y
> and removing EXPERT.
>
It is fine by me, but may I ask to state in the commit message that the patch
can be reverted once the we fix the headers issue? I would like to have symmetry
in enabling vDSOs in between arm64 and compat once everything is fixed.
> Thanks for the quick turnaround.
>
No problem, it is my responsibility to fix the vDSOs on arm64 and compat if
something breaks ;)
--
Regards,
Vincenzo
Powered by blists - more mailing lists