From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>
Cc: james.bottomley@hansenpartnership.com, stephenmcameron@gmail.com,
akpm@linux-foundation.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: document generic scsi host sysfs attributes
Date: Thu, 18 Aug 2011 14:55:59 +0200 [thread overview]
Message-ID: <20110818145559.37cd9e67@stein> (raw)
In-Reply-To: <20110817182047.8821.55211.stgit@beardog.cce.hp.com>
On Aug 17 Stephen M. Cameron wrote:
> What: /sys/bus/scsi/devices/host*/scsi_host/host*/unchecked_isa_dma
> +Date: February, 2003
> +KernelVersion: Unknown
> +Contact: James Bottomley <James.Bottomley@HansenPartnership.com>
> +Description:
> +
> +What: /sys/bus/scsi/devices/host*/scsi_host/host*/proc_name
> +Date: March, 2004
> +KernelVersion: Unknown
> +Contact: James Bottomley <James.Bottomley@HansenPartnership.com>
> +Description:
> +
> +What: /sys/bus/scsi/devices/host*/scsi_host/host*/scan
> +Date: August, 2003
> +KernelVersion: Unknown
> +Contact: James Bottomley <James.Bottomley@HansenPartnership.com>
> +Description:
> + Read only integer which indicates whether the host is an
> + ancient ISA device which therefore requires extra bounce
> + buffering.
The last description obviously belongs to unchecked_isa_dma.
scan is a write-only attribute that may or may not initiate a bus rescan,
I suppose.
proc_name is the "name of proc directory" of a driver, if the driver
maintained one; though it seems all drivers provide proc_name
independently of the obsolete proc interface for driver data.
--
Stefan Richter
-=====-==-== =--- =--=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-08-18 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 18:20 [PATCH] scsi: document generic scsi host sysfs attributes Stephen M. Cameron
2011-08-18 12:55 ` Stefan Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-19 14:44 Stephen M. Cameron
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=20110818145559.37cd9e67@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=scameron@beardog.cce.hp.com \
--cc=stephenmcameron@gmail.com \
/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