Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Chauvet <louis.chauvet@bootlin.com>
To: igt-dev@lists.freedesktop.org
Cc: Louis Chauvet <louis.chauvet@bootlin.com>,
	miquel.raynal@bootlin.com,  thomas.petazzoni@bootlin.com,
	jeremie.dautheribes@bootlin.com,  arthurgrillo@riseup.net,
	seanpaul@google.com, marcheu@google.com,
	 nicolejadeyee@google.com, kamil.konieczny@linux.intel.com
Subject: [PATCH i-g-t] CONTRIBUTING: Add coding style guidelines
Date: Fri, 15 Mar 2024 17:08:37 +0100	[thread overview]
Message-ID: <20240315-add_coding_style-v1-1-50ad93cfa250@bootlin.com> (raw)

As explained in [1], the submitted patches should follow the same style as
the Linux kernel and must be checked against checkpatch.pl, so add this
recommendation in the CONTRIBUTING.md file.

[1]: https://lore.kernel.org/all/20240314170643.77vzqqoie2otyu4w@kamilkon-desk.igk.intel.com/

Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>

To: igt-dev@lists.freedesktop.org
Cc: miquel.raynal@bootlin.com
Cc: thomas.petazzoni@bootlin.com
Cc: jeremie.dautheribes@bootlin.com
Cc: arthurgrillo@riseup.net
Cc: seanpaul@google.com
Cc: marcheu@google.com
Cc: nicolejadeyee@google.com
Cc: kamil.konieczny@linux.intel.com
---
To: igt-dev@lists.freedesktop.org
Cc: miquel.raynal@bootlin.com
Cc: thomas.petazzoni@bootlin.com
Cc: jeremie.dautheribes@bootlin.com
Cc: arthurgrillo@riseup.net
Cc: seanpaul@google.com
Cc: marcheu@google.com
Cc: nicolejadeyee@google.com
Cc: kamil.konieczny@linux.intel.com

Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
---
 CONTRIBUTING.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2ab8a48f6ae9..ec8debb4091e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -78,6 +78,8 @@ Sending Patches
 - Changes to the testcases are automatically tested. Take the results into
   account before merging.
 
+- The coding rules are the same as for the Linux kernel. To check for common
+  style problems, you need to use the kernel's checkpatch.pl script.
 
 Commit Rights
 -------------

---
base-commit: ed47dd9fb6b5be6c88513c2816f0f7cfdd0e02f6
change-id: 20240315-add_coding_style-b755454de958

Best regards,
-- 
Louis Chauvet <louis.chauvet@bootlin.com>


             reply	other threads:[~2024-03-15 16:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 16:08 Louis Chauvet [this message]
2024-03-15 16:35 ` ✓ CI.xeBAT: success for CONTRIBUTING: Add coding style guidelines Patchwork
2024-03-15 16:50 ` [PATCH i-g-t] " Arthur Grillo
2024-03-15 16:54 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-03-18 11:44   ` Kamil Konieczny
2024-03-21  4:28     ` Illipilli, TejasreeX
2024-03-18 11:43 ` [PATCH i-g-t] " Kamil Konieczny
2024-03-18 14:04   ` Jani Nikula
2024-03-20  9:42     ` Louis Chauvet
2024-03-20  9:42   ` Louis Chauvet
2024-03-20  7:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-03-20 15:22 ` [PATCH i-g-t] " Kamil Konieczny
2024-03-20 16:41   ` Louis Chauvet
2024-03-20 17:48 ` ✗ Fi.CI.IGT: failure for " Patchwork

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=20240315-add_coding_style-v1-1-50ad93cfa250@bootlin.com \
    --to=louis.chauvet@bootlin.com \
    --cc=arthurgrillo@riseup.net \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeremie.dautheribes@bootlin.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=marcheu@google.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nicolejadeyee@google.com \
    --cc=seanpaul@google.com \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox