diff options
| author | Rhys Kidd <rhyskidd@gmail.com> | 2018-01-22 23:43:53 -0500 |
|---|---|---|
| committer | Petri Latvala <petri.latvala@intel.com> | 2018-01-23 11:15:08 +0200 |
| commit | 2db1219c13ed80df40fd7e4973beea019b0296d2 (patch) | |
| tree | 7b407e6b11a72d0318191fbef38ba6d29441a91e | |
| parent | f1290e3c55ecd3665a5d77cffeaf3562f3b6b700 (diff) | |
doc: Fix typos in CONTRIBUTING
Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
| -rw-r--r-- | CONTRIBUTING | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING index aa555aa1..5600caaf 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -29,7 +29,7 @@ A short list of contribution guidelines: - Patches need to be reviewed on the mailing list. Exceptions only apply for testcases and tooling for drivers with just a single contributor (e.g. vc4). In this case patches must still be submitted to the mailing list first. - Testcase should preferrably be cross-reviewed by the same people who write and + Testcase should preferably be cross-reviewed by the same people who write and review the kernel feature itself. - When patches from new contributors (without commit access) are stuck, for @@ -38,9 +38,7 @@ A short list of contribution guidelines: contact one of the maintainers (listed in the MAINTAINERS file) and cc the intel-gfx mailing list. -- Especially changes to the testcase should get tested on relevant platforms - before committing. For Intel employees that's best done using PRTS, see the - relevant internal howtos. Everyone else can just run piglit with i-g-t tests - locally. +- Changes to the testcases are automatically tested. Take the results into + account before merging. Happy hacking! |