From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Add a simple doc for selftests
Date: Tue, 12 Feb 2013 15:56:57 -0800 [thread overview]
Message-ID: <20130212155657.86443c7c.akpm@linux-foundation.org> (raw)
In-Reply-To: <1360317764.684151.590003024082.1.gpush@pecola>
On Fri, 08 Feb 2013 18:02:44 +0800
Jeremy Kerr <jk@ozlabs.org> wrote:
> On 08/02/13 07:13, Andrew Morton wrote:
>
> > The general ruleset for selftests is: do as much as you can if you're not
> > root and don't take too long and don't break the build on any
> > architecture and don't cause the top-level "make run_tests" to fail if
> > your feature is unconfigured.
>
> This change adds a little documentation to the tests under
> tools/testing/selftests/, based on akpm's explanation.
Looks nice, thanks ;)
I'm thinking we move it from Documentation/selftests.txt to
tools/testing/selftests/README.txt, where people are more likely to
notice it?
next prev parent reply other threads:[~2013-02-12 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 14:48 [PATCH 0/3 v3] selftests: Add efivarfs tests Jeremy Kerr
2013-02-06 14:48 ` [PATCH 3/3 v3] selftests/efivarfs: Add create-read test Jeremy Kerr
2013-02-06 14:48 ` [PATCH 1/3 v3] selftests: Add tests for efivarfs Jeremy Kerr
2013-02-07 23:13 ` Andrew Morton
2013-02-08 10:02 ` [PATCH] Documentation: Add a simple doc for selftests Jeremy Kerr
2013-02-12 23:56 ` Andrew Morton [this message]
2013-02-08 10:05 ` [PATCH 1/3 v3] selftests: Add tests for efivarfs Jeremy Kerr
2013-02-08 10:08 ` Matt Fleming
2013-02-12 23:50 ` Andrew Morton
2013-02-13 7:32 ` Matt Fleming
2013-02-12 23:48 ` Andrew Morton
2013-02-06 14:48 ` [PATCH 2/3 v3] selftests/efivarfs: Add empty file creation test Jeremy Kerr
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=20130212155657.86443c7c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jk@ozlabs.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