mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tautschnig, Michael" <tautschn@amazon.co.uk>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Andy Lutomirski <luto@amacapital.net>,
	"Tautschnig, Michael" <tautschn@amazon.co.uk>,
	Jann Horn <jannh@google.com>, "x86@kernel.org" <x86@kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Jaswinder Singh <jaswinder@infradead.org>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86: always use SYSCALL_DEFINE*
Date: Wed, 14 Mar 2018 09:43:46 +0000	[thread overview]
Message-ID: <C59EE7A8-35FC-47D6-AB63-33690684310E@amazon.com> (raw)
In-Reply-To: <20180314054802.GC8354@light.dominikbrodowski.net>

Hi Dominik,

> On 14 Mar 2018, at 05:48, Dominik Brodowski <linux@dominikbrodowski.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.




      reply	other threads:[~2018-03-14  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-10 20:55 Tautschnig, Michael
2018-03-10 20:59 ` Tautschnig, Michael
2018-03-11  9:43 ` [PATCH v2] " Tautschnig, Michael
2018-03-13 21:16 ` [PATCH] " Jann Horn
2018-03-13 23:18   ` Andy Lutomirski
2018-03-14  5:48     ` Dominik Brodowski
2018-03-14  9:43       ` Tautschnig, Michael [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C59EE7A8-35FC-47D6-AB63-33690684310E@amazon.com \
    --to=tautschn@amazon.co.uk \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jannh@google.com \
    --cc=jaswinder@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®