From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: "Suzuki Takashi" <suzuki.takashi@gmail.com>,
dhowells@redhat.com, torvalds@osdl.org,
akpm@linux-foundation.org, linux-am33-list@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #2]
Date: Wed, 31 Oct 2007 10:50:48 +0000 [thread overview]
Message-ID: <20071031105048.3d0fbf42@the-village.bc.nu> (raw)
In-Reply-To: <31286.1193785564@redhat.com>
> Can you guarantee there won't be any non-AM33 variants of mn10300 that need
> supporting? An AM34, perhaps?
>
> So basically, the toolchain name should change from am33 to mn10300 by your
> argument.
Given the "i686" toolchain name is wrong (its actually i686 + cmov) there
is a ton of history for the tool chain name not matching up and its even
happened on PC - and there are tools like rpm that have to know about the
mismatches and already cope.
next prev parent reply other threads:[~2007-10-31 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 12:27 David Howells
2007-10-29 12:28 ` [PATCH 1/2] MN10300: Suppress AOUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT " David Howells
2007-10-30 12:57 ` [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel " Suzuki Takashi
2007-10-30 14:14 ` David Howells
2007-10-30 15:10 ` Suzuki Takashi
2007-10-30 16:53 ` David Howells
2007-10-30 17:47 ` DJ Delorie
2007-10-30 21:59 ` Suzuki Takashi
2007-10-30 23:06 ` David Howells
2007-10-31 10:50 ` Alan Cox [this message]
2007-11-02 15:19 ` Suzuki Takashi
[not found] ` <20071029122809.2846.58795.stgit@warthog.procyon.org.uk>
2007-10-30 14:40 ` [Linux-am33-list] [PATCH 2/2] MN10300: Add the MN10300/AM33 architecture to the " Suzuki Takashi
2007-10-30 20:04 ` David Howells
2007-10-31 0:03 ` Suzuki Takashi
2007-10-31 11:46 ` David Howells
2007-11-03 16:07 ` Suzuki Takashi
2007-11-05 15:38 ` David Howells
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=20071031105048.3d0fbf42@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki.takashi@gmail.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®