mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, <linuxppc-dev@ozlabs.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	tuliom@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	murphyp@linux.vnet.ibm.com, schwab@linux-m68k.org,
	sam.bobroff@au1.ibm.com
Subject: Re: Partial revert of "powerpc: Individual System V IPC system calls"
Date: Thu, 17 Dec 2015 21:19:12 +1100 (AEDT)	[thread overview]
Message-ID: <20151217101912.1BF371402C9@ozlabs.org> (raw)
In-Reply-To: <1450263209-11217-1-git-send-email-mpe@ellerman.id.au>

On Wed, 2015-16-12 at 10:53:29 UTC, Michael Ellerman wrote:
> This partially reverts commit a34236155afb1cc41945e58388ac988431bcb0b8.
> 
> While reviewing the glibc patch to exploit the individual IPC calls,
> Arnd & Andreas noticed that we were still requiring userspace to pass
> IPC_64 in order to get the new style IPC API.
> 
> With a bit of cleanup in the kernel we can drop that requirement, and
> instead only provide the new style API, which will simplify things for
> userspace.
> 
> Rather than try and sneak that patch into 4.4, instead we will drop the
> individual IPC calls for powerpc, and merge them again in 4.5 once the
> cleanup patch has gone in.
> 
> Because we've already added sys_mlock2() as syscall #378, we don't do a
> full revert of the IPC calls. Instead we drop the __NR #defines, and
> send those now undefined syscall numbers to sys_ni_syscall(). This
> leaves a gap in the syscall numbers, but we'll reuse them when we merge
> the individual IPC calls.
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Acked-by: Arnd Bergmann <arnd@arndb.de>

Applied to powerpc fixes.

https://git.kernel.org/powerpc/c/2475c362134a0fa5309c7b0f

cheers

      reply	other threads:[~2015-12-17 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 10:53 [PATCH] " Michael Ellerman
2015-12-17 10:19 ` Michael Ellerman [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=20151217101912.1BF371402C9@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=murphyp@linux.vnet.ibm.com \
    --cc=sam.bobroff@au1.ibm.com \
    --cc=schwab@linux-m68k.org \
    --cc=tuliom@linux.vnet.ibm.com \
    /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®