From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux IDE mailing list <linux-ide@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Understanding libata error messages
Date: Thu, 27 Mar 2008 09:53:13 -0700 [thread overview]
Message-ID: <20080327095313.caf2a949.randy.dunlap@oracle.com> (raw)
In-Reply-To: <47EBCD5C.1040402@garzik.org>
On Thu, 27 Mar 2008 12:37:48 -0400 Jeff Garzik wrote:
> I wrote a new wiki page that assists users in understanding the goop
> that libata spits out into your dmesg:
>
> http://ata.wiki.kernel.org/index.php/Libata_error_messages
Good stuff, thanks.
Should we add this URL somewhere in Documentation/ ?
Any suggestions where?
---
~Randy
next prev parent reply other threads:[~2008-03-27 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 16:37 Understanding libata error messages Jeff Garzik
2008-03-27 16:53 ` Randy Dunlap [this message]
[not found] ` <47EBE211.1050802@kcore.org>
2008-03-27 18:51 ` Jeff Garzik
[not found] <fa.lASp3VWtFhbl2bGy0e6Via5Dnvs@ifi.uio.no>
2008-03-28 4:53 ` Robert Hancock
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=20080327095313.caf2a949.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).