From: Chris Zankel <chris@zankel.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Arch <linux-arch@vger.kernel.org>,
Richard Henderson <rth@twiddle.net>, Ian Molton <spyro@f2s.com>,
Russell King <rmk@arm.linux.org.uk>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
Aubrey Li <aubrey.li@analog.com>,
Mikael Starvik <starvik@axis.com>,
David Howells <dhowells@redhat.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Andi Kleen <ak@suse.de>, Tony Luck <tony.luck@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ralf Baechle <ralf@linux-mips.org>,
Matthew Wilcox <matthew@wil.cx>,
Paul Mackerras <paulus@samba.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
Miles Bader <uclinux-v850@lsi.nec.co.jp>
Subject: Re: [PATCH] cross-architecture ELF clean up
Date: Thu, 21 Jun 2007 09:49:46 -0700 [thread overview]
Message-ID: <467AAC2A.8020101@zankel.net> (raw)
In-Reply-To: <20070620230902.387008536@goop.org>
Jeremy,
Could you please add the ELF architecture-magic number for Xtensa (94)
when you finally submit this patch?
Jeremy Fitzhardinge wrote:
> This patch cleans up the ELF headers and their users. It does several
> related things:
> --- /dev/null
> +++ b/include/linux/elf-const.h
> @@ -0,0 +1,222 @@
> +#ifndef _LINUX_ELF_CONST_H
> +#define _LINUX_ELF_CONST_H
> +
> +/* These constants define the various ELF target machines */
> +#define EM_NONE 0
...
> +#define EM_V850 87 /* NEC v850 */
> +#define EM_M32R 88 /* Renesas M32R */
#define EM_XTENSA 94
Thanks,
-Chris
next prev parent reply other threads:[~2007-06-21 17:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070620230854.246399397@goop.org>
2007-06-20 23:08 ` [PATCH] cross-architecture ELF clean up Jeremy Fitzhardinge
2007-06-21 8:20 ` ian
2007-06-21 15:06 ` Jeremy Fitzhardinge
2007-06-21 16:49 ` Chris Zankel [this message]
2007-06-21 18:31 ` Jeremy Fitzhardinge
2007-06-25 9:02 ` David Woodhouse
2007-06-25 12:43 ` Jeremy Fitzhardinge
2007-06-25 13:40 ` Roman Zippel
2007-06-25 13:56 ` Clemens Koller
2007-06-25 14:06 ` Roman Zippel
2007-06-25 13:37 ` Roman Zippel
2007-06-26 19:29 ` Jeremy Fitzhardinge
2007-06-27 23:25 ` Roman Zippel
2007-06-28 15:45 ` Jeremy Fitzhardinge
2007-06-28 21:48 ` Roman Zippel
2007-06-29 14:53 ` Jeremy Fitzhardinge
2007-06-29 18:12 ` Sam Ravnborg
2007-07-01 16:23 ` Jeremy Fitzhardinge
2007-06-25 15:18 ` Roman Zippel
2007-06-26 19:28 ` Jeremy Fitzhardinge
2007-06-29 4:13 ` Paul Mackerras
2007-06-29 5:31 ` Jeremy Fitzhardinge
2007-06-29 4:48 ` Paul Mackerras
2007-06-29 5:31 ` Jeremy Fitzhardinge
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=467AAC2A.8020101@zankel.net \
--to=chris@zankel.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=aubrey.li@analog.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=hskinnemoen@atmel.com \
--cc=jeremy@goop.org \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=spyro@f2s.com \
--cc=starvik@axis.com \
--cc=tony.luck@intel.com \
--cc=uclinux-v850@lsi.nec.co.jp \
--cc=ysato@users.sourceforge.jp \
/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.