From: Dave Jones <davej@codemonkey.org.uk>
To: Osamu Tomita <tomita@cinet.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCHSET 1/25] add support for PC-9800 architecture (apm)
Date: Fri, 18 Oct 2002 18:47:20 +0100 [thread overview]
Message-ID: <20021018174720.GA3884@suse.de> (raw)
In-Reply-To: <20021019015619.A1516@precia.cinet.co.jp>
On Sat, Oct 19, 2002 at 01:56:19AM +0900, Osamu Tomita wrote:
> This patchset adds support for NEC PC-9800 architecture, against 2.5.43.
> Fixed bad things commented by Russell King.
>
> PC-9800 series machines are made by NEC. But sold only in japan.
> Formaly, they were best sellers in japan.
> We port linux for PC-9800 since 2.1.57.
>
> I'm testing 2.5.43 with this patchset on some boxes.
> - PC-9800 i586 UP with IDE drive
> - PC-9800 i686 SMP with SCSI drive
> - AT compatible with IDE drive (patch applied but not set CONFIG_PC9800).
> They works well.
> We are doing our best, patchset has no effect on original without configuring
> for PC-9800.
> Please apply this patchset.
The biggest sticking point as far as I'm concerned with this patchset
is the source readability after applying it.
Something really needs to be done about the #if pollution this
patch adds before it's ready for inclusion. The whole patchset adds
over 700 #if's/ifdefs/ifndefs.
In a lot of cases you even do this..
+#ifdef PC9800
+ unsigned long foo
+#endif
...
+#ifdef PC9800
+ code using foo
+#endif
where foo could have been moved inside a {} section in the ifdef
which is using it. This is one of the simpler cases, there's
also a whole bunch of stuff where you don't even need ifdefs at all
(around #defines for example)
I see you've gone to the effort of making sure the generated code
is the same if PC9800 support is compiled out, which is good.
The next step is to get the source clean enough that those that
don't care about PC9800 don't have to hurt their eyes untangling
a web of #if's.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-10-18 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 16:56 [PATCHSET 1/25] add support for PC-9800 architecture (apm) Osamu Tomita
2002-10-18 17:47 ` Dave Jones [this message]
2002-10-19 0:47 ` [PATCHSET 1/25] add support for PC-9800 architecture Osamu Tomita
2002-10-23 11:03 ` [PATCHSET 1/25] add support for PC-9800 architecture (apm) Geert Uytterhoeven
2002-10-23 15:44 ` Osamu Tomita
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=20021018174720.GA3884@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tomita@cinet.co.jp \
--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 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.