On 2024-03-30 19:39, Sam Ravnborg wrote:
> Hi Arnd,
>
> On Sat, Mar 30, 2024 at 11:19:37AM +0100, Arnd Bergmann wrote:
>> On Sat, Mar 30, 2024, at 10:57, Sam Ravnborg via B4 Relay wrote:
>>> Nick Bowler reported that sparc64 failed to bring all his CPU's online,
>>> and that turned out to be an easy fix.
>>>
>>> The sparc64 build was rather noisy with a lot of warnings which had
>>> irritated me enough to go ahead and fix them.
>>> With this set of patches my arch/sparc/ is almost warning free for
>>> all{no,yes,mod}config + defconfig builds.
>>
>> Patches 1-9 look good to me,
>>
>> Acked-by: Arnd Bergmann <arnd@xxxxxxxx>
> Thanks!
Picking up patches 1-8 to my for-next with
Reviewed-by: Andreas Larsson <andreas@xxxxxxxxxxx>
Tested-by: Andreas Larsson <andreas@xxxxxxxxxxx>
and, having run it only on single core qemu, patch 9 with
Reviewed-by: Andreas Larsson <andreas@xxxxxxxxxxx>
>>
>>> There is one warning about "clone3 not implemented", which I have ignored.
>>>
>>> The warning fixes hides the fact that sparc64 is not yet y2038 prepared,
>>> and it would be preferable if someone knowledgeable would fix this
>>> poperly.
>>
>> The clone3 bug has been around for ages, it's probably not even that
>> hard to fix and just needs a little bit of testing.
> I looked briefly and it involves a better understanding of the window
> register manipulation than what I have today.
>
>>
>> If anyone wants to work on the time64 support for the vdso, I can
>> explain the details for how it's done.
>
> I am happy to type the patches but need to rely on others for testing.
> Anything to help me get started would be super.
I'm not picking up patch 10 at the moment, but it would be really nice
to get allmodconfig builds to not fail due to prototype Werrors.
Thanks,
Andreas
