All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] put symbolic links between drivers and modules in the sysfs tree
Date: Sat, 25 Sep 2004 09:46:21 -0700	[thread overview]
Message-ID: <20040925164621.GA9098@kroah.com> (raw)
In-Reply-To: <20040925073819.GT23987@parcelfarce.linux.theplanet.co.uk>

On Sat, Sep 25, 2004 at 08:38:19AM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Mon, Sep 20, 2004 at 01:29:44PM -0400, James Bottomley wrote:
> > This functionality is essential for us to work out which drivers are
> > supplied by which modules.  We use this in turn to work out which
> > modules are necessary to find the root device (and hence what
> > initrd/initramfs needs to insert).
> 
> So what will your userland code do when you run it on a system with
> non-modular kernel currently running?
> 
> IOW, that's a fundamentally broken interface - you really want the same
> information regardless of modular vs. built-in.

I agree, and Rusty has some pending patches that provide that
information for all drivers built into the system.  When they are
merged, this symlink will be created for those also (with a bit of
tweaking, but it will happen.)

thanks,

greg k-h

      parent reply	other threads:[~2004-09-25 16:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 17:29 [RFC] put symbolic links between drivers and modules in the sysfs tree James Bottomley
2004-09-22 23:04 ` Greg KH
2004-09-22 23:06   ` Greg KH
2004-09-22 23:40     ` Greg KH
2004-09-25  7:38 ` viro
2004-09-25  8:05   ` Herbert Xu
2004-09-25  8:21     ` Arjan van de Ven
2004-09-25 13:16       ` James Bottomley
2004-09-25 13:14   ` James Bottomley
2004-09-26 10:37     ` Herbert Xu
2004-09-26 10:37       ` Herbert Xu
2004-09-26 13:09       ` James Bottomley
2004-09-25 16:46   ` Greg KH [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=20040925164621.GA9098@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.