[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <C59EE7A8-35FC-47D6-AB63-33690684310E@amazon.com>
Date: Wed, 14 Mar 2018 09:43:46 +0000
From: "Tautschnig, Michael" <tautschn@...zon.co.uk>
To: Dominik Brodowski <linux@...inikbrodowski.net>
CC: Andy Lutomirski <luto@...capital.net>,
"Tautschnig, Michael" <tautschn@...zon.co.uk>,
Jann Horn <jannh@...gle.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Thomas Gleixner" <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jaswinder Singh <jaswinder@...radead.org>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] x86: always use SYSCALL_DEFINE*
Hi Dominik,
> On 14 Mar 2018, at 05:48, Dominik Brodowski <linux@...inikbrodowski.net> wrote:
> [...]
> ... the ioperm change is already in mainline (did an equivalent change a
> couple of days ago), but the sigreturn/rt_sigreturn changes still seem
> useful. Could you send a fresh patch with just these two changes; and -- if
> the x86 maintainers agree -- I will push it with my syscall-related changes?
Thanks for all this cleanup work. I have posted the {rt_,}sigreturn changes as
"[PATCH] x86/sigreturn: use SYSCALL_DEFINE0".
Best,
Michael
Amazon Web Services UK Limited. Registered in England and Wales with registration number 08650665 with its registered office at 1 Principal Place, Worship Street, London, EC2A 2FA, United Kingdom.
Powered by blists - more mailing lists