From: Michael Ellerman <mpe@ellerman•id.au>
To: David Long <dave.long@linaro•org>
Cc: "H. Peter Anvin" <hpa@zytor•com>,
Andy Lutomirski <luto@amacapital•net>,
Anton Blanchard <anton@samba•org>,
Behan Webster <behanw@converseincode•com>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Eric Paris <eparis@redhat•com>,
Heiko Carstens <heiko.carstens@de•ibm.com>,
Ingo Molnar <mingo@redhat•com>, Jan Willeke <willeke@de•ibm.com>,
Kees Cook <keescook@chromium•org>,
Martin Schwidefsky <schwidefsky@de•ibm.com>,
Nikolay Borisov <Nikolay.Borisov@arm•com>,
Oleg Nesterov <oleg@redhat•com>,
Paul Mackerras <paulus@samba•org>,
Richard Kuo <rkuo@codeaurora•org>,
Robert Richter <rric@kernel•org>,
Roland McGrath <roland@hack•frob.com>,
Russell King <linux@arm•linux.org.uk>, Tejun Heo <tj@kernel•org>,
Thomas Gleixner <tglx@linutronix•de>,
Will Deacon <will.deacon@arm•com>,
linux-arm-kernel@lists•infradead.org,
linux-hexagon@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-s390@vger•kernel.org, linux-sh@vger•kernel.org,
linux390@de•ibm.com, linuxppc-dev@lists•ozlabs.org,
x86@kernel•org
Subject: Re: [PATCH 1/2] Move the pt_regs_offset struct definition from arch to common include file
Date: Fri, 19 Jun 2015 14:19:43 +1000 [thread overview]
Message-ID: <1434687583.23771.5.camel@ellerman.id.au> (raw)
In-Reply-To: <1434386579-6045-2-git-send-email-dave.long@linaro.org>
On Mon, 2015-06-15 at 12:42 -0400, David Long wrote:
> From: "David A. Long" <dave.long@linaro•org>
>
> The pt_regs_offset structure is used for HAVE_REGS_AND_STACK_ACCESS_API
> feature and has identical definitions in four different arch ptrace.h
> include files. It seems unlikely that definition would ever need to be
> changed regardless of architecture so lets move it into
> include/linux/ptrace.h.
>
> Signed-off-by: David A. Long <dave.long@linaro•org>
> ---
> arch/powerpc/kernel/ptrace.c | 5 -----
Built and booted on powerpc, but is there an easy way to actually test the code
paths in question?
Acked-by: Michael Ellerman <mpe@ellerman•id.au>
cheers
next prev parent reply other threads:[~2015-06-19 4:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 16:42 [PATCH 0/2] Consolidate redundant register/stack access code David Long
2015-06-15 16:42 ` [PATCH 1/2] Move the pt_regs_offset struct definition from arch to common include file David Long
2015-06-16 13:17 ` Rob Herring
2015-06-17 18:30 ` David Long
2015-06-30 3:29 ` Michael Ellerman
2015-07-22 4:46 ` David Long
2015-07-22 5:11 ` Michael Ellerman
2015-07-22 13:30 ` David Long
2015-06-19 4:19 ` Michael Ellerman [this message]
2015-06-19 14:12 ` David Long
2015-06-19 16:58 ` Kees Cook
2015-06-26 18:35 ` David Long
2015-06-23 3:32 ` Michael Ellerman
2015-06-23 13:48 ` David Long
2015-06-24 4:07 ` Michael Ellerman
2015-06-24 13:49 ` David Long
2015-06-15 16:42 ` [PATCH 2/2] Consolidate redundant register/stack access code David Long
2015-06-18 18:13 ` rkuo
2015-06-15 20:44 ` [PATCH 0/2] " Kees Cook
2015-06-15 20:58 ` David Long
2015-06-16 8:12 ` Martin Schwidefsky
2015-06-16 17:39 ` Will Deacon
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=1434687583.23771.5.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=Nikolay.Borisov@arm$(echo .)com \
--cc=anton@samba$(echo .)org \
--cc=behanw@converseincode$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=dave.long@linaro$(echo .)org \
--cc=eparis@redhat$(echo .)com \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=hpa@zytor$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-hexagon@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linux390@de$(echo .)ibm.com \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=luto@amacapital$(echo .)net \
--cc=mingo@redhat$(echo .)com \
--cc=oleg@redhat$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=rkuo@codeaurora$(echo .)org \
--cc=roland@hack$(echo .)frob.com \
--cc=rric@kernel$(echo .)org \
--cc=schwidefsky@de$(echo .)ibm.com \
--cc=tglx@linutronix$(echo .)de \
--cc=tj@kernel$(echo .)org \
--cc=will.deacon@arm$(echo .)com \
--cc=willeke@de$(echo .)ibm.com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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