From: Christoph Hellwig <hch@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] s390 update (1/9): s390 arch fixes.
Date: Wed, 26 Mar 2003 20:04:02 +0000 [thread overview]
Message-ID: <20030326200402.A21308@infradead.org> (raw)
In-Reply-To: <OF80FD93D6.AA8C5DBA-ONC1256CF5.00589668@de.ibm.com>; from schwidefsky@de.ibm.com on Wed, Mar 26, 2003 at 05:20:39PM +0100
> s390 and s390x are similar at the first glance. But if you look in detail
> you will notice that there are a lot of small differences. A simple diff
> of the files that are present in both arch folger gives a patch of 5600
> lines.
Now actually take a look at this diff :) The biggest part is that the
s390 compat files exist only on s390x and the math-emu dir only exists
on s390, that's just a matter of conditionally compiling the files.
Then there's of course slightly different assembly, this is just different
but can be abstracted out nicely. In C code there's lots of spurious
differences that don't make any sense (like using the proper type on s390x
but soething that doesn't matter on s390, commenting changes, etc..).
There's still some real differences of course, but it's really a small
amount of the code size.
next prev parent reply other threads:[~2003-03-26 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 16:20 Martin Schwidefsky
2003-03-26 20:04 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-27 12:55 Martin Schwidefsky
2003-03-27 12:17 Martin Schwidefsky
2003-03-27 12:28 ` Christoph Hellwig
[not found] <20030326163014$65d6@gated-at.bofh.it>
[not found] ` <20030326201008$0568@gated-at.bofh.it>
2003-03-26 22:44 ` Arnd Bergmann
2003-03-27 8:46 ` Christoph Hellwig
2003-03-26 15:05 Martin Schwidefsky
2003-03-26 15:45 ` Christoph Hellwig
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=20030326200402.A21308@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@transmeta.com \
/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®