From: David Daney <ddaney.cavm@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Ungerer <gerg@snapgear.com>
Subject: Re: [PATCH] Remove v850 from linux/elf-em.h
Date: Tue, 15 Mar 2016 16:22:16 -0700 [thread overview]
Message-ID: <56E89928.1010008@gmail.com> (raw)
In-Reply-To: <56E87A63.8020703@landley.net>
On 03/15/2016 02:10 PM, Rob Landley wrote:
> From: Rob Landley <rob@landley.net>
>
> The v850 port was removed by commits f606ddf42fd4 and 07a887d399b8 in 2008.
> These #defines are not used in the current kernel.
>
> Signed-off-by: Rob Landley <rob@landley.net>
> ---
> include/uapi/linux/elf-em.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/include/uapi/linux/elf-em.h b/include/uapi/linux/elf-em.h
> index b56dfcf..c3fdfe7 100644
> --- a/include/uapi/linux/elf-em.h
> +++ b/include/uapi/linux/elf-em.h
> @@ -30,7 +30,6 @@
> #define EM_X86_64 62 /* AMD x86-64 */
> #define EM_S390 22 /* IBM S/390 */
> #define EM_CRIS 76 /* Axis Communications 32-bit embedded processor */
> -#define EM_V850 87 /* NEC v850 */
Can you do this to userspace visible files?
I thought only additions and obvious corrections were allowed. Removing
symbols could cause build breakage for something.
> #define EM_M32R 88 /* Renesas M32R */
> #define EM_MN10300 89 /* Panasonic/MEI MN10300, AM33 */
> #define EM_OPENRISC 92 /* OpenRISC 32-bit embedded processor */
> @@ -50,8 +49,6 @@
> */
> #define EM_ALPHA 0x9026
>
> -/* Bogus old v850 magic number, used by old tools. */
> -#define EM_CYGNUS_V850 0x9080
> /* Bogus old m32r magic number, used by old tools. */
> #define EM_CYGNUS_M32R 0x9041
> /* This is the old interim value for S/390 architecture */
>
next prev parent reply other threads:[~2016-03-15 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 21:10 [PATCH] Remove v850 from linux/elf-em.h Rob Landley
2016-03-15 23:22 ` David Daney [this message]
2016-03-16 7:11 ` Rob Landley
2016-03-17 22:09 ` David Daney
2016-03-18 2:32 ` Rob Landley
2016-03-18 17:46 ` David Daney
2016-03-19 1:15 ` Rob Landley
2016-03-21 16:39 ` David Daney
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=56E89928.1010008@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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.