From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, miquel.raynal@bootlin.com,
thomas.petazzoni@bootlin.com, jeremie.dautheribes@bootlin.com,
arthurgrillo@riseup.net, seanpaul@google.com, marcheu@google.com,
nicolejadeyee@google.com
Subject: Re: [PATCH i-g-t] CONTRIBUTING: Add coding style guidelines
Date: Wed, 20 Mar 2024 17:41:04 +0100 [thread overview]
Message-ID: <ZfsRoFUsUbRZrfIH@localhost.localdomain> (raw)
In-Reply-To: <20240320152233.gydl3lwmexdoto5o@kamilkon-desk.igk.intel.com>
Le 20/03/24 - 16:22, Kamil Konieczny a écrit :
> Hi Louis,
> On 2024-03-15 at 17:08:37 +0100, Louis Chauvet wrote:
> > 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/
> >
>
> There is code style mensioned at line 13, grep -n -A1 kernel CONTRIBUTING.md
> gives (in second match):
I missed it, I think it's because I read this section too fast and jumped
to "Sending Patches".
> 13:- The code should follow kernel coding style:
> 14: https://www.kernel.org/doc/html/latest/process/coding-style.html
>
> So maybe place it after that line?
Yes, I can move the checkpatch sentence+command here.
But as the "The Code" section deals in more detail with the internal
workings of the igt, I think it's better to keep something in "Sending
Patches", like:
- Your patch must adhere the code style defined in "The Code".
This way, the section "Sending Patches" can serve as a "checklist" (accept
the licence, use igt prefix, check the style).
Additionally, as the documentation is automaticaly build, maybe it
might be useful to include the following point:
- If you're add new tests, please ensure that you've written the
documentation before submitting by running:
ninja -C build igt-gpu-tools-doc
Otherwise, auto-builders will complain if the documentation is missing.
I have a question regarding the documentation. [1] explains that
igt_describe is deprecated, but CONTRIBUTION.md and igt_describe() doc
don't explain the "new" testplan documentation. Perhaps I could revise
"The Code" section to include:
- All new test must be documented in two ways:
- A call to igt_describe(), just before the test. This should provide
a concise description of the test's purpose, and it will be
displayed during execution.
- A testplan comment at the top of the file. This should
provide further explanation of the test's functionality and is
utilized in reporting tools.
Please refer to [1] for more details
[1]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/blob/master/docs/test_documentation.md?ref_type=heads
Thanks,
Louis Chauvet
> Regards,
> Kamil
>
> > 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>
> >
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-03-20 16:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 16:08 [PATCH i-g-t] CONTRIBUTING: Add coding style guidelines Louis Chauvet
2024-03-15 16:35 ` ✓ CI.xeBAT: success for " 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 [this message]
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=ZfsRoFUsUbRZrfIH@localhost.localdomain \
--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 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.