From: Brian King <brking@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Christoph Hellwig <hch@lst.de>,
jejb@steeleye.com, James.Smart@Emulex.Com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] drop some attibutes from the FC transport class
Date: Wed, 19 Jan 2005 17:03:39 -0600 [thread overview]
Message-ID: <41EEE74B.2090907@us.ibm.com> (raw)
In-Reply-To: <20050119224016.GA5086@kroah.com>
Greg KH wrote:
> On Wed, Jan 19, 2005 at 01:39:24PM -0800, Mike Anderson wrote:
>
>>Greg KH [greg@kroah.com] wrote:
>>
>>>On Wed, Jan 19, 2005 at 06:13:57PM +0100, Christoph Hellwig wrote:
>>>
>>>>I think the hardware_version, firmware_version, rom_version and
>>>>driver_version don't belong into the FC transport class, there's
>>>>nothign specific to FC or even SCSI specific in them.
>>>
>>>Then put them in the individual driver (not the driver_version one
>>>though, that belongs as a MODULE_VERSION() paramater).
>>
>>Are there plans to export MODULE_VERSION info in /sys/module/*/ ? I
>>believe the intent was to try and use libsysfs to access these attributes
>>/ info.
>
>
> I had a patch to do that around here somewhere, but I think it was
> rejected as people can get the same info by using 'modinfo' instead.
> You know, the old, "use a userspace tool instead of wasting kernel
> memory" argument :)
That's too bad. modinfo will only tell you information about the driver
that modprobe finds, which is not necessarily what is currently loaded
in kernel memory.
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2005-01-19 23:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 17:13 [PATCH] drop some attibutes from the FC transport class Christoph Hellwig
2005-01-19 17:21 ` Greg KH
2005-01-19 18:38 ` Brian King
2005-01-19 18:45 ` Greg KH
2005-01-19 22:59 ` Brian King
2005-01-19 21:39 ` Mike Anderson
2005-01-19 22:40 ` Greg KH
2005-01-19 23:03 ` Brian King [this message]
2005-01-19 23:03 ` Christoph Hellwig
2005-01-19 23:08 ` Greg KH
2005-01-19 23:15 ` Matt Domsch
2005-01-19 23:42 ` Greg KH
2005-01-20 5:12 ` Matt Domsch
2005-01-20 14:41 ` Greg KH
2005-01-26 6:05 ` [PATCH 2.6.11-rc2] modules: add version and srcversion to sysfs Matt Domsch
2005-01-26 9:22 ` Andreas Gruenbacher
2005-01-26 14:09 ` Matt Domsch
2005-01-26 16:38 ` Andreas Gruenbacher
2005-01-27 17:03 ` Matt Domsch
2005-01-27 17:41 ` Bill Davidsen
2005-01-26 14:32 ` Paulo Marques
2005-01-27 2:10 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 17:25 [PATCH] drop some attibutes from the FC transport class James.Smart
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=41EEE74B.2090907@us.ibm.com \
--to=brking@us.ibm.com \
--cc=James.Smart@Emulex.Com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=jejb@steeleye.com \
--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 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.