From: Michael Ellerman <mpe@ellerman.id.au>
To: "David A. Long" <dave.long@linaro.org>,
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: [v2, 1/2] Move the pt_regs_offset struct definition from arch to common include file
Date: Tue, 18 Aug 2015 20:43:30 +1000 (AEST) [thread overview]
Message-ID: <20150818104330.B24DC14032B@ozlabs.org> (raw)
In-Reply-To: <1437971974-2434-2-git-send-email-dave.long@linaro.org>
On Mon, 2015-27-07 at 04:39:33 UTC, "David A. Long" wrote:
> From: "David A. Long" <dave.long@linaro.org>
>
> The pt_regs_offset structure is used for the 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, along with macros commonly used to access it.
Thanks for cleaning this up. Tested successfully on powerpc.
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
cheers
next prev parent reply other threads:[~2015-08-18 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 4:39 [PATCH v2 0/2] Consolidate redundant register/stack access code David Long
2015-07-27 4:39 ` [PATCH v2 1/2] Move the pt_regs_offset struct definition from arch to common include file David Long
2015-08-18 10:43 ` Michael Ellerman [this message]
2015-07-27 4:39 ` [PATCH v2 2/2] Consolidate redundant register/stack access code David Long
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=20150818104330.B24DC14032B@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=x86@kernel.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).