public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Matt Domsch <Matt_Domsch@Dell.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Sun, 29 Sep 2002 19:27:58 +0100	[thread overview]
Message-ID: <20020929192758.D15924@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0209291315010.28578-100000@chaos.physics.uiowa.edu>; from kai-germaschewski@uiowa.edu on Sun, Sep 29, 2002 at 01:20:44PM -0500

On Sun, Sep 29, 2002 at 01:20:44PM -0500, Kai Germaschewski wrote:
> Let me add that there are currently two places where arch specific drivers
> appear, eg:
> 
> 	arch/{cris,um}/drivers/
> and
> 	drivers/{s390,macintosh,acorn}/
> 
> I think it'd be nice to decide on one way or the other. The first place 
> has the advantage of putting all arch-specific stuff into one place, the 
> second one makes it (IMO) cleaner to share drivers between e.g. s390 and 
> s390x, or possibly i386/x86_64 in the future.

The ARM port used to have arch/arm/drivers/{block,char,net,sound} but
this was decried by _other_ people in the ARM community to be too
painful, and I was literally hounded into moving them into drivers.

I don't want to go back to arch/arm/drivers now, thanks.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-09-29 18:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com>
2002-09-27 21:30 ` [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Matt Domsch
2002-09-27 22:33   ` Greg KH
2002-09-29 16:11   ` Dave Jones
2002-09-29 16:18     ` Zwane Mwaikambo
2002-09-29 16:44     ` Alan Cox
2002-09-29 18:20     ` Kai Germaschewski
2002-09-29 18:27       ` Russell King [this message]
2002-09-29 18:52         ` Dave Jones
2002-10-01  1:55   ` Patrick Mochel
2002-10-01  3:37 Matt_Domsch
  -- strict thread matches above, loose matches on Subject: below --
2002-09-30  4:32 Matt_Domsch
2002-09-11 19:09 Matt_Domsch
2002-09-12 18:00 ` Patrick Mochel
2002-09-12 18:48   ` Matt Domsch
2002-09-10 22:43 Matt_Domsch
2002-09-09  1:17 Matt_Domsch
2002-09-04  0:54 Matt_Domsch
2002-09-04  1:09 ` Daniel Phillips
2002-09-04  4:17   ` Greg KH
2002-09-08  0:39     ` Patrick Mochel
2002-09-03 22:05 Matt Domsch
2002-09-03 23:29 ` Daniel Phillips
2002-09-04  4:35 ` Andre Hedrick
2002-09-04 16:02   ` Matt Domsch

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=20020929192758.D15924@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Matt_Domsch@Dell.com \
    --cc=davej@codemonkey.org.uk \
    --cc=kai-germaschewski@uiowa.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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