linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rkuo@codeaurora.org (rkuo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Consolidate redundant register/stack access code
Date: Thu, 18 Jun 2015 13:13:05 -0500	[thread overview]
Message-ID: <20150618181304.GA9557@codeaurora.org> (raw)
In-Reply-To: <1434386579-6045-3-git-send-email-dave.long@linaro.org>

On Mon, Jun 15, 2015 at 12:42:59PM -0400, David Long wrote:
> From: "David A. Long" <dave.long@linaro.org>
> 
> Several architectures have identical or functionally equivalent code
> implementing parts of the HAVE_REGS_AND_STACK_ACCESS_API feature.  Move
> that code out of the architecture directories.
> 
> Signed-off-by: David A. Long <dave.long@linaro.org>
> ---
>  arch/arm/include/asm/ptrace.h          |  6 ---
>  arch/arm/kernel/ptrace.c               | 67 +-------------------------------
>  arch/hexagon/include/uapi/asm/ptrace.h |  3 --
>  arch/powerpc/include/asm/ptrace.h      | 38 ------------------
>  arch/powerpc/kernel/ptrace.c           | 34 +----------------
>  arch/s390/include/asm/ptrace.h         |  3 --
>  arch/s390/kernel/ptrace.c              | 70 ++++++++++------------------------
>  arch/sh/include/asm/ptrace.h           | 39 -------------------
>  arch/sh/kernel/Makefile                |  2 +-
>  arch/sh/kernel/ptrace.c                | 33 ----------------
>  arch/sh/kernel/ptrace_32.c             |  2 +-
>  arch/sh/kernel/ptrace_64.c             |  2 +-
>  arch/x86/include/asm/ptrace.h          | 37 ------------------
>  arch/x86/kernel/ptrace.c               | 34 +----------------
>  include/linux/ptrace.h                 | 42 ++++++++++++++++++++
>  kernel/ptrace.c                        | 38 ++++++++++++++++++
>  16 files changed, 107 insertions(+), 343 deletions(-)
>  delete mode 100644 arch/sh/kernel/ptrace.c
> 

(And in some cases, the architecture didn't have the code in the first place!)

For Hexagon:

Acked-by: Richard Kuo <rkuo@codeaurora.org>

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-06-18 18:13 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
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 [this message]
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=20150618181304.GA9557@codeaurora.org \
    --to=rkuo@codeaurora.org \
    --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).