From: Sean Paul <seanpaul@chromium.org>
To: intel-gfx@lists.freedesktop.org
Cc: seanpaul@google.com
Subject: [PATCH i-g-t v3 1/2] CONTRIBUTING: Fix spelling mistake and line length
Date: Mon, 8 Jan 2018 10:55:20 -0500 [thread overview]
Message-ID: <20180108155521.246175-1-seanpaul@chromium.org> (raw)
Noticed while I was reading it. Makes for a good first contribution, I
guess.
Changes in v2:
- None
Changes in v3:
- None
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
---
CONTRIBUTING | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 561c5dd8..ca2ed8a5 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -18,13 +18,13 @@ A short list of contribution guidelines:
on its first invocation.
-- intel-gpu-tools is MIT lincensed and we require contributions to follow the
+- intel-gpu-tools is MIT licensed and we require contributions to follow the
developer's certificate of origin: http://developercertificate.org/
- When submitting new testcases please follow the naming conventions documented
- in the generated documentation. Also please make full use of all the helpers and
- convenience macros provided by the igt library. The semantic patch lib/igt.cocci
- can help with the more automatic conversions.
+ in the generated documentation. Also please make full use of all the helpers
+ and convenience macros provided by the igt library. The semantic patch
+ lib/igt.cocci can help with the more automatic conversions.
- 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).
--
2.16.0.rc0.223.g4a4ac83678-goog
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-01-08 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 15:55 Sean Paul [this message]
2018-01-08 15:55 ` [PATCH i-g-t v3 2/2] kms_content_protection: Add Content Protection test Sean Paul
2018-02-14 15:09 ` Chris Wilson
2018-01-08 16:31 ` ✓ Fi.CI.BAT: success for series starting with [v3,1/2] CONTRIBUTING: Fix spelling mistake and line length Patchwork
2018-01-08 20:03 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-17 10:20 ` [PATCH i-g-t v3 1/2] " Petri Latvala
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=20180108155521.246175-1-seanpaul@chromium.org \
--to=seanpaul@chromium.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=seanpaul@google.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.