All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: "Patrick Ale" <patrick.ale@gmail.com>
Cc: "Randy Dunlap" <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: libsata tests started
Date: Sat, 10 Feb 2007 20:35:04 +0000	[thread overview]
Message-ID: <20070210203504.129b35ac@localhost.localdomain> (raw)
In-Reply-To: <8d158e1f0702101214j603e1880i7eae2d94b446bc0b@mail.gmail.com>

> > libsata == libata ?
> I don't think there is a seperate libata, it's all put under libsata
> if I understand the working correctly (Alan, don't sue me if I am
> wrong).

Right umm "Your honor the gentleman is human, this is not acceptable" ?

It is in drivers/ata the files are libata-* so it's normally known as
"libata", so libsata == libata.
 
> Maybe it *IS* a nice idea to outline some standard tests that
> developers want to have carried out or some specific tests to trace
> bugs or test if a patch/fix does its work.. But that's not up to me, I
> am not a coder, I can do some very basic stuff in C, that's where
> programming ends for me, unless it's shell scripting.

Beating the crap out of it using it for real work is one excellent form
of testing. We aren't yet at the point of only worrying about benchmark
tuning and corner cases.

Alan

  reply	other threads:[~2007-02-10 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 16:22 libsata tests started Patrick Ale
2007-02-10 19:41 ` Randy Dunlap
2007-02-10 20:14   ` Patrick Ale
2007-02-10 20:35     ` Alan [this message]
2007-02-10 20:32       ` Patrick Ale
2007-02-10 22:04         ` Patrick Ale
2007-02-10 22:23           ` Michal Piotrowski
2007-02-13  8:31             ` Patrick Ale
2007-02-15  4:57               ` Tejun Heo
2007-02-15 16:16                 ` Patrick Ale
2007-02-15 16:18                 ` Patrick Ale
2007-02-15 19:37                   ` Ioan Ionita
2007-02-15 20:07                     ` Patrick Ale

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=20070210203504.129b35ac@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick.ale@gmail.com \
    --cc=randy.dunlap@oracle.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.