public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: Frederic TEMPORELLI <frederic.temporelli@bull.net>,
	linux-scsi@vger.kernel.org
Subject: Re: proc_name in sysfs
Date: Mon, 11 Apr 2005 12:52:15 +0100	[thread overview]
Message-ID: <20050411115215.GB13154@infradead.org> (raw)
In-Reply-To: <42563AC4.4050605@torque.net>

On Fri, Apr 08, 2005 at 06:03:16PM +1000, Douglas Gilbert wrote:
> >The real problem is that someone decided to export the proc_name in sysfs.
> >It's supposed to be only procfs-specific but someone violated that rule.
> 
> Forget the "proc_" part. It is effectively the lld_name.
> 
> Allowing the LLD to name itself to the scsi subsystem
> makes sense, especially when the LLD is made up of several
> kernel modules. See my previous example comparing the
> output of lsscsi -H and scan_host.sh .

In theory we have ->name for that, but people have decided to put really
verbose stuff in there.  A module name is important, not just for scsi.

James once had a proposal where the scsi_host can link to the module in
sysfs, which is the right thing and needed for other things like mkinitrd
aswell.

  reply	other threads:[~2005-04-11 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 11:40 proc_name in sysfs Frederic TEMPORELLI
2005-04-06 18:36 ` Patrick Mansfield
2005-04-07  1:06   ` Douglas Gilbert
2005-04-07  6:35     ` Frederic TEMPORELLI
2005-04-07  8:17       ` Douglas Gilbert
2005-04-08  0:02       ` Patrick Mansfield
2005-04-08  7:37         ` Frederic TEMPORELLI
2005-04-08  0:00     ` Patrick Mansfield
2005-04-08  6:46 ` Christoph Hellwig
2005-04-08  8:03   ` Douglas Gilbert
2005-04-11 11:52     ` Christoph Hellwig [this message]
2005-04-11 14:19       ` James Bottomley

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=20050411115215.GB13154@infradead.org \
    --to=hch@infradead.org \
    --cc=dougg@torque.net \
    --cc=frederic.temporelli@bull.net \
    --cc=linux-scsi@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