public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	Mike Frysinger <vapier@gentoo.org>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	David Howells <dhowells@redhat.com>,
	Tony Luck <tony.luck@intel.com>,
	Hirokazu Takata <takata@linux-m32r.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Michal Simek <monstr@monstr.eu>, Jonas Bonn <jonas@southpole.se>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Richard Kuo <rkuo@codeaurora.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Lennox Wu <lennox.wu@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Paul Mundt <lethal@linux-sh.org>, Chris Zankel <chris@zankel.net>,
	Chris Metcalf <cmetcalf@tilera.com>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	Russell King <linux@arm.linux.org.uk>
Subject: Re: [RFC][CFT] what's in signal.git queue
Date: Thu, 14 Feb 2013 20:52:22 +1100	[thread overview]
Message-ID: <1360835542.6646.5.camel@pasglop> (raw)
In-Reply-To: <20130214012539.GQ4503@ZenIV.linux.org.uk>

On Thu, 2013-02-14 at 01:25 +0000, Al Viro wrote:
> Mostly it's a unification of signal-related syscalls, both native and compat
> ones; by the end of it we shouldn't have syscalls left in normal
> arch/*/kernel/signal*.c - there are some exceptions due to genuine weirdness
> of arch-specific calling conventions, but that's rare.  Another (somewhat
> related) story in there is more compat_sys_something() getting switched to
> COMPAT_SYSCALL_DEFINE, giving us proper argument validation wrappers.  Not
> everything got switched, of course, but a lot of those guys has been.

FYI. I'm going to be off to some meeting & bringup work in the US for two weeks
so expect little responsiveness from me on this until after I'm back (March 1st).

Cheers,
Ben.



  reply	other threads:[~2013-02-14  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14  1:25 [RFC][CFT] what's in signal.git queue Al Viro
2013-02-14  9:52 ` Benjamin Herrenschmidt [this message]
2013-02-14 10:23 ` Martin Schwidefsky
2013-02-15  7:29 ` Jonas Bonn
2013-02-20 19:36 ` rkuo

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=1360835542.6646.5.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=catalin.marinas@arm.com \
    --cc=chris@zankel.net \
    --cc=cmetcalf@tilera.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=hskinnemoen@gmail.com \
    --cc=jejb@parisc-linux.org \
    --cc=jesper.nilsson@axis.com \
    --cc=jonas@southpole.se \
    --cc=lennox.wu@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=monstr@monstr.eu \
    --cc=rkuo@codeaurora.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=takata@linux-m32r.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vapier@gentoo.org \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=ysato@users.sourceforge.jp \
    /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