From: Matt_Domsch@Dell.com
To: kai-germaschewski@uiowa.edu, davej@codemonkey.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: RE: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Sun, 29 Sep 2002 23:32:22 -0500 [thread overview]
Message-ID: <20BF5713E14D5B48AA289F72BD372D68C1E8E0@AUSXMPC122.aus.amer.dell.com> (raw)
> drivers/{s390,macintosh,acorn}/
> makes it (IMO) cleaner to share drivers between
> e.g. s390 and s390x, or possibly i386/x86_64 in the future.
The i386 EDD "driver" could probably be shared with x86-64, I hadn't thought
about it before. Likewise the IA64 efivars driver *may* eventually be
shared with x86 or others if Intel's plans come to fruition. So I'd vote
for something in drivers/ rather than arch/ for such shareable modules. I'm
open to moving each of these if told where the "right" place should be.
Neither are char or block drivers, so those don't make sense - purely
driverfs/proc interfaces. Nor are they "bus" drivers ala ide or scsi.
drivers/misc is empty and I think people want to keep it that way...
Some ideas for these:
drivers/i386
drivers/efi
Thoughts?
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer, Architect
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next reply other threads:[~2002-09-30 4:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 4:32 Matt_Domsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 3:37 [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Matt_Domsch
[not found] <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com>
2002-09-27 21:30 ` 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
2002-09-29 18:52 ` Dave Jones
2002-10-01 1:55 ` Patrick Mochel
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=20BF5713E14D5B48AA289F72BD372D68C1E8E0@AUSXMPC122.aus.amer.dell.com \
--to=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;
as well as URLs for NNTP newsgroup(s).