From: heiko.carstens@de.ibm.com (Heiko Carstens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] all: s390: move compat_wrappers.c from arch/s390/kernel to kernel/
Date: Thu, 25 Feb 2016 09:52:27 +0100 [thread overview]
Message-ID: <20160225085227.GD3980@osiris> (raw)
In-Reply-To: <1456338854-14901-5-git-send-email-ynorov@caviumnetworks.com>
On Wed, Feb 24, 2016 at 09:34:13PM +0300, Yury Norov wrote:
> Some syscalls are declared conditionally, so corresponding wrappers
> are conditional accordingly.
>
> Signed-off-by: Yury Norov <ynorov@caviumnetworks.com>
> ---
> arch/s390/kernel/Makefile | 2 +-
> arch/s390/kernel/compat_wrapper.c | 129 -----------------------------
> kernel/Makefile | 1 +
> kernel/compat_wrapper.c | 170 ++++++++++++++++++++++++++++++++++++++
> 4 files changed, 172 insertions(+), 130 deletions(-)
> delete mode 100644 arch/s390/kernel/compat_wrapper.c
> create mode 100644 kernel/compat_wrapper.c
Generated code looks identical on s390 and of course still works!
next prev parent reply other threads:[~2016-02-25 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 18:34 [PATCH v2 0/5] all: s390: make compat wrappers the generic solution Yury Norov
2016-02-24 18:34 ` [PATCH 1/5] all: syscall wrappers: add documentation Yury Norov
2016-02-24 18:34 ` [PATCH 2/5] all: introduce COMPAT_WRAPPER option and enable it for s390 Yury Norov
2016-02-25 8:49 ` Heiko Carstens
2016-02-25 20:19 ` Yury Norov
2016-02-25 22:10 ` Heiko Carstens
2016-02-24 18:34 ` [PATCH 3/5] all: s390: move wrapper infrastructure to generic headers Yury Norov
2016-02-25 8:51 ` Heiko Carstens
2016-02-25 20:23 ` Yury Norov
2016-02-25 22:20 ` Heiko Carstens
2016-02-24 18:34 ` [PATCH 4/5] all: s390: move compat_wrappers.c from arch/s390/kernel to kernel/ Yury Norov
2016-02-25 8:52 ` Heiko Carstens [this message]
2016-02-25 20:27 ` Yury Norov
2016-02-24 18:34 ` [PATCH 5/5] all: wrap needed syscalls in generic unistd Yury Norov
2016-02-25 8:54 ` [PATCH v2 0/5] all: s390: make compat wrappers the generic solution Heiko Carstens
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=20160225085227.GD3980@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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).