Re: Can we drop upstream Linux x32 support?

My impression is it was mostly a desire to reuse existing x86_64 system calls as much as possible without modification or additional compat layer work. The 64-bit time requirement seems to have come from an lkml discussion, which has quite a bit of interesting background about x32:

Re: Can we drop upstream Linux x32 support?

On Thu, Dec 13, 2018 at 9:39 AM Olof Johansson wrote: > > On Tue, Dec 11, 2018 at 9:40 AM Linus Torvalds > wrote: > > > > On Mon, Dec 10, 2018 at 5:23 PM Andy Lutomirski wrote: > > > > > > I'm seriously considering sending a patch to remove x32 support from > > > upstream Linux. Here are some

Re: Sparse warnings on GENMASK + arm32

> From: "Stephen Boyd" > To: linux-spa...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Sent: Tuesday, 25 July, 2017 9:30:20 PM > Subject: Sparse warnings on GENMASK + arm32 > > I see sparse warning when I check a clk driver file in the kernel > on a 32-bit ARM

Re: Sparse warnings on GENMASK + arm32

> From: "Stephen Boyd" > To: linux-spa...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Sent: Tuesday, 25 July, 2017 9:30:20 PM > Subject: Sparse warnings on GENMASK + arm32 > > I see sparse warning when I check a clk driver file in the kernel > on a 32-bit ARM build. > >

[PATCH] percpu: eliminate two sparse warnings

Fix two cases where a __percpu pointer cast drops __percpu. Signed-off-by: Lance Richardson <lrich...@redhat.com> --- arch/x86/include/asm/percpu.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/arch/x86/include/asm/percpu.h b/arch/x86/include/asm/percpu.h index e

[PATCH] percpu: eliminate two sparse warnings

Fix two cases where a __percpu pointer cast drops __percpu. Signed-off-by: Lance Richardson --- arch/x86/include/asm/percpu.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/arch/x86/include/asm/percpu.h b/arch/x86/include/asm/percpu.h index e02e3f8..84f58de 100644