From: Greg KH <greg@kroah.com>
To: Asai Thambi S P <asamymuthupa@micron.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sam Bradshaw <sbradshaw@micron.com>
Subject: Re: [PATCH 2/5] mtip32xx: Add new sysfs entry 'status' and fix restart port
Date: Fri, 6 Apr 2012 14:44:26 -0700 [thread overview]
Message-ID: <20120406214426.GA12772@kroah.com> (raw)
In-Reply-To: <4F7F615B.80305@micron.com>
On Fri, Apr 06, 2012 at 02:34:19PM -0700, Asai Thambi S P wrote:
> On 4/6/2012 11:12 AM, Asai Thambi S P wrote:
>
> > On 4/5/2012 6:10 PM, Greg KH wrote:
> >
> >> On Thu, Apr 05, 2012 at 02:00:12PM -0700, Asai Thambi S P wrote:
> >>>
> >>> * Add support for detecting the following device status
> >>> - write protect
> >>> - over temp (thermal shutdown)
> >>> * New sysfs entry 'status' created for this device, possible values - online, write_protect, thermal_shutdown
> >>
> >> All new (and existing) sysfs files must be documented in
> >> Documentation/ABI/ please do so for these new ones when you add them to
> >> the kernel.
> >
> >
> > I was not aware of this. Thanks. I will a add new file for mtip32xx driver.
> >
>
>
> Greg,
>
> The sysfs entry for the disk is
> /sys/block/rssda -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/block/rssda
>
> Should I use /sys/block/<disk>/<entry> or
> /sys/devices/.../block/<disk>/entry> in the doc file?
What do the existing api files show for block devices?
next prev parent reply other threads:[~2012-04-06 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 21:00 [PATCH 2/5] mtip32xx: Add new sysfs entry 'status' and fix restart port Asai Thambi S P
2012-04-06 1:10 ` Greg KH
2012-04-06 18:12 ` Asai Thambi S P
2012-04-06 21:34 ` Asai Thambi S P
2012-04-06 21:44 ` Greg KH [this message]
2012-04-06 22:03 ` Asai Thambi S P
2012-04-06 23:30 ` Greg KH
2012-04-07 0:28 ` Asai Thambi S P
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=20120406214426.GA12772@kroah.com \
--to=greg@kroah.com \
--cc=asamymuthupa@micron.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=sbradshaw@micron.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 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.