On Fri, Jul 11, 2014 at 11:12 AM, Andi Kleen <[email protected]> wrote: >> diff --git a/arch/x86/include/uapi/asm/sigcontext.h >> b/arch/x86/include/uapi/asm/sigcontext.h >> index 076b11f..df9908b 100644 >> --- a/arch/x86/include/uapi/asm/sigcontext.h >> +++ b/arch/x86/include/uapi/asm/sigcontext.h > > I don't think renaming fields in uapi/asm is acceptable. These > are likely used by user programs and you'll break compiles.
Hmm. That's a fair point. On the other hand, any user code that uses these fields explicitly may already be broken, since the current names of these fields rather strongly imply that they do something. Is there any clear policy on minor API breaks in the UAPI headers that don't affect ABI? --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
