From: Greg KH <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next 3/3] mei: add ABI documentation for fw_status exported through sysfs
Date: Wed, 26 Nov 2014 19:05:57 -0800 [thread overview]
Message-ID: <20141127030557.GC8656@kroah.com> (raw)
In-Reply-To: <1416409300-14431-3-git-send-email-tomas.winkler@intel.com>
On Wed, Nov 19, 2014 at 05:01:40PM +0200, Tomas Winkler wrote:
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> ---
> Documentation/ABI/testing/sysfs-class-mei | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-mei b/Documentation/ABI/testing/sysfs-class-mei
> index 0ec8b8178c41..61d45f03e09b 100644
> --- a/Documentation/ABI/testing/sysfs-class-mei
> +++ b/Documentation/ABI/testing/sysfs-class-mei
> @@ -14,3 +14,11 @@ Description:
> The /sys/class/mei/meiN directory is created for
> each probed mei device
>
> +What: /sys/class/mei/meiN/fw_status
> +Date: Nov 2014
> +KernelVersion: 3.19
> +Contact: Tomas Winkler <tomas.winkler@intel.com>
> +Description: Display fw status registers content for applications
> + that monitor fw health. The registers meaning is platform
> + dependent.
That's not documenting what is in the file, "platform dependent" is
lame.
prev parent reply other threads:[~2014-11-27 3:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 15:01 [char-misc-next 1/3] mei: read and print all six FW status registers Tomas Winkler
2014-11-19 15:01 ` [char-misc-next 2/3] mei: export fw status registers through sysfs Tomas Winkler
2014-11-27 3:04 ` Greg KH
2014-11-27 3:05 ` Greg KH
2014-11-19 15:01 ` [char-misc-next 3/3] mei: add ABI documentation for fw_status exported " Tomas Winkler
2014-11-27 3:05 ` Greg KH [this message]
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=20141127030557.GC8656@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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