From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5] support for NCR voyager 343x/345x/4100/51xx architecture
Date: Thu, 27 Dec 2001 08:08:03 -0600 [thread overview]
Message-ID: <200112271408.fBRE84d19791@localhost.localdomain> (raw)
In-Reply-To: Message from Rik van Riel <riel@conectiva.com.br> of "Sun, 23 Dec 2001 22:58:05 -0200." <Pine.LNX.4.33L.0112232256180.12081-100000@imladris.surriel.com>
riel@conectiva.com.br said:
> One thing which worries me is that the number of these machines is
> very small, so the code could temporarily go the way the SGI visws
> code went.
> It would be nice if this code was split out in such a way that it
> won't have any impact on the maintainability of the mainstream code,
> so even if the voyager folks go on holiday, normal Linux development
> can continue and the resulting bitrot will be limited to just the
> voyager code.
I would like to do this. I didn't do it for the 2.4 series because such a
patch would have been very difficult to maintain. I'll see if I can separate
the VISW code as well.
James
next prev parent reply other threads:[~2001-12-27 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-23 19:13 [PATCH: NEW ARCHITECTURE FOR 2.5] support for NCR voyager 343x/345x/4100/51xx architecture James Bottomley
2001-12-24 0:10 ` Dave Jones
2001-12-27 14:09 ` James Bottomley
2001-12-27 15:33 ` Dave Jones
2001-12-24 0:58 ` Rik van Riel
2001-12-27 14:08 ` James Bottomley [this message]
2001-12-27 15:34 ` Dave Jones
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=200112271408.fBRE84d19791@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--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