linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Tautschnig, Michael" <tautschn@amazon.co.uk>,
	"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>,
	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/sigreturn: use SYSCALL_DEFINE0
Date: Wed, 14 Mar 2018 21:36:45 +0100	[thread overview]
Message-ID: <20180314203645.GA21437@light.dominikbrodowski.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1803142102300.1946@nanos.tec.linutronix.de>

On Wed, Mar 14, 2018 at 09:04:13PM +0100, Thomas Gleixner wrote:
> On Wed, 14 Mar 2018, Tautschnig, Michael wrote:
> 
> > All definitions of syscalls in x86 except for those patched here have
> > already been using the appropriate SYSCALL_DEFINE*.
> 
> Dominik, do you have more urgent stuff queued in that area?
> 
> If yes, please add: Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> 
> If not, I simply route it through x86/urgent for 4.16.

Thanks for asking! Nothing urgent from my side, only stuff for 4.17, so it
would be great if you could route it through x86/urgent.

Thanks,
	Dominik

  reply	other threads:[~2018-03-14 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  9:41 [PATCH] x86/sigreturn: use SYSCALL_DEFINE0 Tautschnig, Michael
2018-03-14 20:04 ` Thomas Gleixner
2018-03-14 20:36   ` Dominik Brodowski [this message]
2018-03-19 20:17 ` kbuild test robot
2018-03-19 22:27 ` kbuild test robot

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=20180314203645.GA21437@light.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jaswinder@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tautschn@amazon.co.uk \
    --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;
as well as URLs for NNTP newsgroup(s).