public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Matt_Domsch@Dell.com, linux-kernel@vger.kernel.org,
	Patrick Mochel <mochel@osdl.org>
Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Tue, 3 Sep 2002 21:17:05 -0700	[thread overview]
Message-ID: <20020904041705.GC3739@kroah.com> (raw)
In-Reply-To: <E17mOfS-0005nm-00@starship>

On Wed, Sep 04, 2002 at 03:09:12AM +0200, Daniel Phillips wrote:
> On Wednesday 04 September 2002 02:54, Matt_Domsch@Dell.com wrote:
> > > How about providing an example of how you'd export the root 
> > > via driverfs,
> > > with a view to educating those of us who are still don't have 
> > > much of a clue how driverfs fits in with big picture?
> > 
> > Right now that includes me which is why I used proc for now. :-)
> 
> Maybe we should prevail upon the driverfs axis to provide some guidance.

Sweet, we're an axis now!  That's much better than the other terms Pat
and I have been called in the past...  And everyone knows what's the
next size jump up from axis :)

So here's how driverfs fits into the big picture in one sentance:

	Anything that does not have to do with processes 
	will go into driverfs.

So in this example, we are exporting a number of boot devices as the
bios told us, so apply the rule stated above, and determine if it should
go into /proc or not[1].

thanks,

greg k-h

[1]  Yes, it's still a bit difficult to figure how to add files to
driverfs, if you aren't starting with a "struct device" or "struct
device_driver", but I have seen some very nice documentation on how to
do it properly written by Pat involving a wonderful example of beer, and
I'm sure that once he gets back into internet connectivity range, he'll
be updating it and adding it to the Documentation directory.  That
should be by the end of the week or so.

  reply	other threads:[~2002-09-04  4:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04  0:54 [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Matt_Domsch
2002-09-04  1:09 ` Daniel Phillips
2002-09-04  4:17   ` Greg KH [this message]
2002-09-08  0:39     ` Patrick Mochel
  -- strict thread matches above, loose matches on Subject: below --
2002-10-01  3:37 Matt_Domsch
2002-09-30  4:32 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-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=20020904041705.GC3739@kroah.com \
    --to=greg@kroah.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=phillips@arcor.de \
    /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