From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Mike Robak" <mrobak@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: libATA error message doc
Date: Fri, 5 Oct 2007 21:51:47 +0100 [thread overview]
Message-ID: <20071005215147.42bdc01d@the-village.bc.nu> (raw)
In-Reply-To: <p737im15q8s.fsf@bingen.suse.de>
> I always found that quite convenient. Putting at least a summary in Documentation
> would probably user-friendly. It tends to be hard to find stuff in specifications,
> especially if you're not very familiar with the standard.
There are over 100 commands, and the status bits can only be read in
combination and according to some interpretation rules - it would be
quite a long document. The standards are also all publically available in
this case, albeit not neccessarily the most interesting read
AFAIK there is a patch queued to print some of the data in a more user
friendly format.
prev parent reply other threads:[~2007-10-05 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 17:39 Mike Robak
2007-10-03 17:54 ` Jeff Garzik
2007-10-03 18:24 ` Alan Cox
2007-10-05 19:13 ` Andi Kleen
2007-10-05 20:51 ` Alan Cox [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=20071005215147.42bdc01d@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrobak@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
all inboxes | Powered by JetHome®