The issue with that is that "compat" is a cross-architecture feature of the kernel to handle *some* 32-on-64 bit ABI translations. x32 uses *some* but not all of the compat machinery. It is already confusing when you introduce more than two ABIs (e.g. x32 or MIPS n32) and we need a way to be able to be specific. I suggest using i386 or just use ia32 as a legacy symbol name. On June 18, 2015 11:14:45 AM PDT, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: >On Jun 18, 2015 7:49 AM, "Brian Gerst" <brgerst@xxxxxxxxx> wrote: >> >> As long as there is no confusion between this and X32, I am fine with >it. > >I would suggest that we use "compat" for the traditional 32-bit x86 >code, >and x32 for the x32/ones. That sounds very natural and unambiguous to >me.. > > Linus -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|