From: Dave Martin <Dave.Martin@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Alan Hayward <alan.hayward@arm.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: [PATCH v2 0/2] arm64/sve: UAPI: Disentangle ptrace.h from sigcontext.h
Date: Fri, 4 Jan 2019 13:09:49 +0000 [thread overview]
Message-ID: <1546607391-3850-1-git-send-email-Dave.Martin@arm.com> (raw)
This patch refactors the UAPI header definitions for the Arm SVE
extension to avoid multiple-definition problems when userspace mixes its
own sigcontext.h definitions with the kernel's ptrace.h (which is
apparently routine).
A common backend header is created to hold common definitions, suitably
namespaced.
The extra header guard in sve_context.h was considered redundant and is
now gone, so patch 1 (kbuild: install_headers.sh: Strip _UAPI from
#if-defined() guards) from the previous version of the series has been
dropeed.
Dave Martin (2):
arm64/sve: ptrace: Fix SVE_PT_REGS_OFFSET definition
arm64/sve: Disentangle <uapi/asm/ptrace.h> from
<uapi/asm/sigcontext.h>
arch/arm64/include/uapi/asm/ptrace.h | 39 ++++++++++-----------
arch/arm64/include/uapi/asm/sigcontext.h | 56 +++++++++++++++----------------
arch/arm64/include/uapi/asm/sve_context.h | 53 +++++++++++++++++++++++++++++
3 files changed, 99 insertions(+), 49 deletions(-)
create mode 100644 arch/arm64/include/uapi/asm/sve_context.h
--
2.1.4
next reply other threads:[~2019-01-04 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 13:09 Dave Martin [this message]
2019-01-04 13:09 ` [PATCH v2 1/2] arm64/sve: ptrace: Fix SVE_PT_REGS_OFFSET definition Dave Martin
2019-01-04 13:09 ` [PATCH v2 2/2] arm64/sve: Disentangle <uapi/asm/ptrace.h> from <uapi/asm/sigcontext.h> Dave Martin
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=1546607391-3850-1-git-send-email-Dave.Martin@arm.com \
--to=dave.martin@arm.com \
--cc=alan.hayward@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szabolcs.nagy@arm.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).