Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 1/5] README: Reword a few sentences
Date: Tue, 26 Mar 2013 15:24:35 +0000	[thread overview]
Message-ID: <1364311479-20669-2-git-send-email-damien.lespiau@intel.com> (raw)
In-Reply-To: <1364311479-20669-1-git-send-email-damien.lespiau@intel.com>

To be a bit more correct (they were understandable though).

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
---
 README | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README b/README
index be29177..c484a93 100644
--- a/README
+++ b/README
@@ -27,17 +27,17 @@ tests/
 	Run this tests with "make test" as root from this directory. Note that
 	no other drm clients (X server) may run.
 
-	"make test" only runs a default of test usefull for regression testing.
-	Other tests not run are:
+	"make test" only runs a default set of tests and is useful for
+	regression testing. Other tests not run are:
 	- tests that might hang the gpu, see HANG in Makefile.am
 	- gem_stress, a stress test suite. Look at the source for all the
 	  various options.
 	- testdisplay is only run in the default mode. testdisplay has tons of
-	  options to test different kms functionality, again read the source of
+	  options to test different kms functionality, again read the source for
 	  the details.
 
 	The more comfortable way to run tests is with piglit. First grab piglit
-	from
+	from:
 
 	git://anongit.freedesktop.org/piglit
 
-- 
1.7.11.7

  reply	other threads:[~2013-03-26 15:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 15:24 Craft a list of tests to run in simulation (and tune them) Damien Lespiau
2013-03-26 15:24 ` Damien Lespiau [this message]
2013-03-26 15:24 ` [PATCH i-g-t 2/5] lib: Rename IGT_QUICK to IGT_SIMULATION Damien Lespiau
2013-03-26 15:24 ` [PATCH i-g-t 3/5] tests: Use IGT_SIMULATION to tune the list of tests to run Damien Lespiau
2013-03-26 15:38   ` Daniel Vetter
2013-03-26 17:00     ` Ben Widawsky
2013-03-27  0:24       ` Daniel Vetter
2013-03-27  2:54         ` Sun, Yi
2013-04-01  7:21         ` Sun, Yi
2013-04-02 17:06           ` Ben Widawsky
2013-04-02 17:16             ` Damien Lespiau
2013-04-02 17:38               ` Daniel Vetter
2013-03-26 15:24 ` [PATCH i-g-t 4/5] tests: Instrument tests run in simulation to run quickly Damien Lespiau
2013-03-26 15:24 ` [PATCH i-g-t 5/5] build: Make grep silent with running make test Damien Lespiau

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=1364311479-20669-2-git-send-email-damien.lespiau@intel.com \
    --to=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.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