From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] s390 update (1/9): s390 arch fixes.
Date: Wed, 26 Mar 2003 17:20:39 +0100 [thread overview]
Message-ID: <OF80FD93D6.AA8C5DBA-ONC1256CF5.00589668@de.ibm.com> (raw)
> It looks you do exactly the same changes to both s390 and s390x. A
closer
> look at the arch directories shows that about 95% of the code is exactly
> the same. Can you remove the s390x dir and abstract out the few
differences
> into a config option?
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. Compare this to the 11500 lines these files have in total. So the
code is definitly NOT 95% the same. Further the arch folder is not the
only place to look for s390 files. You need to consider include/asm
as well. Overall it is not an easy task. You have a point though that it
would be very nice to have common files for all s390/s390x files, not just
for the device drivers. If I have lots of time someday I probably will
try it but for now it way too much effort.
blue skies,
Martin
next reply other threads:[~2003-03-26 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 16:20 Martin Schwidefsky [this message]
2003-03-26 20:04 ` Christoph Hellwig
-- 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=OF80FD93D6.AA8C5DBA-ONC1256CF5.00589668@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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®