From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Move the EM_AARCH64 definition to uapi/linux/elf-em.h
Date: Thu, 2 May 2013 14:27:56 +0100 [thread overview]
Message-ID: <20130502132756.GD20730@arm.com> (raw)
In-Reply-To: <1367495778-6406-1-git-send-email-alonid@stratoscale.com>
On Thu, May 02, 2013 at 12:56:18PM +0100, Dan Aloni wrote:
> Signed-off-by: Dan Aloni <alonid@stratoscale.com>
> CC: Catalin Marinas <catalin.marinas@arm.com>
> ---
> arch/arm64/include/asm/elf.h | 2 --
> include/uapi/linux/elf-em.h | 1 +
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> (fixed the commit message)
>
> diff --git a/arch/arm64/include/asm/elf.h b/arch/arm64/include/asm/elf.h
> index fe32c0e..b3da1c1 100644
> --- a/arch/arm64/include/asm/elf.h
> +++ b/arch/arm64/include/asm/elf.h
> @@ -33,8 +33,6 @@ typedef unsigned long elf_greg_t;
> typedef elf_greg_t elf_gregset_t[ELF_NGREG];
> typedef struct user_fpsimd_state elf_fpregset_t;
>
> -#define EM_AARCH64 183
> -
> /*
> * AArch64 static relocation types.
> */
> diff --git a/include/uapi/linux/elf-em.h b/include/uapi/linux/elf-em.h
> index 8e2b7ba..bc946e9 100644
> --- a/include/uapi/linux/elf-em.h
> +++ b/include/uapi/linux/elf-em.h
> @@ -34,6 +34,7 @@
> #define EM_MN10300 89 /* Panasonic/MEI MN10300, AM33 */
> #define EM_BLACKFIN 106 /* ADI Blackfin Processor */
> #define EM_TI_C6000 140 /* TI C6X DSPs */
> +#define EM_AARCH64 183 /* ARM 64 bit */
> #define EM_FRV 0x5441 /* Fujitsu FR-V */
> #define EM_AVR32 0x18ad /* Atmel AVR32 */
Will you do the same for arch/arm? There is EM_ARM defined under
arch/arm and arch/arm64 (elf.h).
--
Catalin
next prev parent reply other threads:[~2013-05-02 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 11:56 [PATCH] Move the EM_AARCH64 definition to uapi/linux/elf-em.h Dan Aloni
2013-05-02 13:27 ` Catalin Marinas [this message]
2013-05-05 8:24 ` [PATCH] Move the EM_ARM and EM_AARCH64 definitions " Dan Aloni
2013-08-28 13:24 ` [PATCH repost-for-3.12] " Dan Aloni
2013-08-28 14:47 ` Catalin Marinas
2013-08-30 10:09 ` Catalin Marinas
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=20130502132756.GD20730@arm.com \
--to=catalin.marinas@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.