From: Christoph Hellwig <hch@infradead.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Mark Haverkamp <markh@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] 2.6 aacraid: Add sysfs files for aacraid adapter information (re-diff)
Date: Mon, 23 May 2005 14:46:33 +0100 [thread overview]
Message-ID: <20050523134633.GA14207@infradead.org> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458B0132B6EC@otce2k01.adaptec.com>
On Mon, May 23, 2005 at 07:56:58AM -0400, Salyzyn, Mark wrote:
> >Again please remove the prefix. Also what does kernel version mean in
> >this context?
>
> This is the kernel running in the Firmware of the Adapter.
shouldn't we call this fw_version or firmware_version then?
> I would be concerned about "kernel_version" confusion in the namespace
> of the /sys/ filesystem. Dropping the prefix is not an issue, but do we
> have documented naming standards for driver & firmware specific details?
Unfortunately not. I tried to get these attributes standardized at the
driver core level, but gregkh vetoed that.
The first scsi driver with lots of version attributes is the Emulex lpfc
driver so it might help to follow that one.
next prev parent reply other threads:[~2005-05-23 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 11:56 [PATCH] 2.6 aacraid: Add sysfs files for aacraid adapter information (re-diff) Salyzyn, Mark
2005-05-23 12:20 ` Arjan van de Ven
2005-05-23 13:46 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 11:35 Salyzyn, Mark
2005-05-23 19:12 Salyzyn, Mark
2005-05-17 20:34 Mark Haverkamp
2005-05-22 16:54 ` Christoph Hellwig
2005-05-23 18:36 ` Mark Haverkamp
2005-05-23 18:46 ` Christoph Hellwig
2005-05-23 20:49 ` Mark Haverkamp
2005-05-24 3:30 ` Matt Domsch
2005-05-24 14:18 ` Mark Haverkamp
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=20050523134633.GA14207@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=markh@osdl.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