Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alex deVries <adevries@engsoc.carleton.ca>,
	SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: Moving drivers/sgi around
Date: Tue, 9 Feb 1999 22:31:55 +0100	[thread overview]
Message-ID: <19990209223155.B1509@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.3.96.990208190349.11444F-100000@lager.engsoc.carleton.ca>; from Alex deVries on Mon, Feb 08, 1999 at 07:06:22PM -0500

On Mon, Feb 08, 1999 at 07:06:22PM -0500, Alex deVries wrote:
> Are there any objections to me moving drivers/sgi and merging them into
> the 'correct' places?  The places in question are:
[...]
> Any objections?

not really, but I don't like it either. As long as the drivers in drivers/sgi
aren't usefull for other architectures, I would leave them, where they are.
There is enough different stuff sitting in drivers/char, which should
be sorted out and stuffed into better subdirectories.

I'm even not sure, whether my decision to put newport_con into drivers/video
was the right one. But at least drivers/video contains only driver dedicated 
to the same thing,which is to provide a console.

Thomas.

-- 
   This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
                                        [Martin `MJ' Mares on linux-kernel]

      parent reply	other threads:[~1999-02-09 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-09  0:06 Moving drivers/sgi around Alex deVries
1999-02-09 15:09 ` Eric Kimminau
1999-02-09 21:31 ` Thomas Bogendoerfer [this message]

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=19990209223155.B1509@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.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