linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: 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 12:18:42 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209291217540.24805-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <20020929161144.GA19948@suse.de>

On Sun, 29 Sep 2002, Dave Jones wrote:

> On Fri, Sep 27, 2002 at 04:30:29PM -0500, Matt Domsch wrote:
>  >  arch/i386/kernel/edd.c           |  522 +++++++++++++++++++++++++++++++++++++++
>  >  arch/i386/kernel/i386_ksyms.c    |    6 
>  >  arch/i386/kernel/setup.c         |   20 +
> 
> Something that's been bothering me for a while, has been the
> proliferation of 'driver' type things appearing in arch/i386/kernel/
> My initial thought was to move the various CPU related 'drivers'
> (msr,cpuid,bluesmoke,microcode) to arch/i386/cpu/  [1]
> but I'm now wondering if an arch/i386/driver/ would be a better alternative.
> 
> Opinions?

Then again, drivers/char has some x86 specific drivers too (e.g. RNGs), 
perhaps it really should get dumped in drivers/

	Zwane
-- 
function.linuxpower.ca


  reply	other threads:[~2002-09-29 16:14 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 [this message]
2002-09-29 16:44     ` Alan Cox
2002-09-29 18:20     ` Kai Germaschewski
2002-09-29 18:27       ` Russell King
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=Pine.LNX.4.44.0209291217540.24805-100000@montezuma.mastecende.com \
    --to=zwane@linuxpower.ca \
    --cc=Matt_Domsch@Dell.com \
    --cc=davej@codemonkey.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).