On 02/03/2015 12:58 AM, David Drysdale wrote: > On Tue, Feb 3, 2015 at 3:53 AM, Michael Ellerman <mpe@xxxxxxxxxxxxxx> wrote: >> On systems which don't implement sys_execveat(), this test produces a >> lot of output. >> >> Add a check at the beginning to see if the syscall is present, and if >> not just note one error and return. >> >> When we run on a system that doesn't implement the syscall we will get >> ENOSYS back from the kernel, so change the logic that handles >> __NR_execveat not being defined to also use ENOSYS rather than -ENOSYS. >> >> Signed-off-by: Michael Ellerman <mpe@xxxxxxxxxxxxxx> > > Acked-by: David Drysdale <drysdale@xxxxxxxxxx> Thanks Michael, and David. I will queue this for 3.20 -- Shuah -- Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America (Silicon Valley) shuahkh@xxxxxxxxxxxxxxx | (970) 217-8978 -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
