All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH RFC 0/3] docs: add documentation for checkpatch
Date: Sun, 24 Jan 2021 17:20:00 +0100	[thread overview]
Message-ID: <CAKXUXMzvQVud9qiZby3rznLS=JGd+6MKkC8Yrj7X_Bec9YZmmQ@mail.gmail.com> (raw)
In-Reply-To: <CABJPP5C8U-nmrqggR=Ea3drNF9VxqfisG49sVcNQfufTYejp+g@mail.gmail.com>

On Sun, Jan 24, 2021 at 4:29 PM Dwaipayan Ray <dwaipayanray1@gmail.com> wrote:
>
> On Sun, Jan 24, 2021 at 8:49 PM Dwaipayan Ray <dwaipayanray1@gmail.com> wrote:
> >
> > This patch series serves to introduce a documentation for kernel script
> > checkpatch.pl (scripts/checkpatch.pl).
> >
> > A top level tools directory has been created in docs which shall contain
> > the documentation related to the kernel tools and scripts.
> >
> > This documentation shall be progressively updated by future patches to
> > document all the message types in checkpatch. Consecutively this
> > documentation itself will be parsed by checkpatch to generate verbose
> > messages.
> >
> > Dwaipayan Ray (3):
> >   docs: add documentation for checkpatch
> >   docs: add documentation for checkpatch
> >   docs: add documentation for checkpatch
> >
> >  Documentation/index.rst            |  11 ++
> >  Documentation/tools/checkpatch.rst | 271 +++++++++++++++++++++++++++++
> >  Documentation/tools/index.rst      |  10 ++
> >  3 files changed, 292 insertions(+)
> >  create mode 100644 Documentation/tools/checkpatch.rst
> >  create mode 100644 Documentation/tools/index.rst
> >
> > --
> > 2.30.0
> >
>
> Hey Lukas,
> This patch series serves to introduce the checkpatch documentation.
> A part of this documentation will be used by checkpatch, I am working
> on that right now. Subsequently all the message types can be documented
> slowly.
>
> The initial plan is to parse the part between
> .. CHECKPATCH_START and .. CHECKPATCH_END.
>

Plan sounds reasonable, we will refine as we go.

Go ahead and implement the checkpatch.pl feature to parse this file
and output the description, and send it as RFC to Joe as well, but
point out what is important to you for his opinion (I think you care
if the checkpatch.pl implementation can be done that way) and what
will we refine and completely rewrite as we move forward (the
documentation is really much more work in progress).

> As for the documentation itself, it would be great to have your review on it!
> I could send the pdfdocs as well if you need it.
>

All fine, I can pick this patch series and generate the documentation
locally myself.

Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2021-01-24 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 15:19 [Linux-kernel-mentees] [PATCH RFC 0/3] docs: add documentation for checkpatch Dwaipayan Ray
2021-01-24 15:19 ` [Linux-kernel-mentees] [PATCH RFC 1/3] " Dwaipayan Ray
2021-01-24 16:41   ` Lukas Bulwahn
2021-01-24 16:53     ` Dwaipayan Ray
2021-01-24 16:57       ` Lukas Bulwahn
2021-01-24 15:19 ` [Linux-kernel-mentees] [PATCH RFC 2/3] " Dwaipayan Ray
2021-01-24 15:19 ` [Linux-kernel-mentees] [PATCH RFC 3/3] " Dwaipayan Ray
2021-01-24 16:38   ` Lukas Bulwahn
2021-01-24 16:46     ` Dwaipayan Ray
2021-01-24 16:53       ` Lukas Bulwahn
2021-01-24 15:29 ` [Linux-kernel-mentees] [PATCH RFC 0/3] " Dwaipayan Ray
2021-01-24 16:20   ` Lukas Bulwahn [this message]
2021-01-24 16:51 ` Lukas Bulwahn

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='CAKXUXMzvQVud9qiZby3rznLS=JGd+6MKkC8Yrj7X_Bec9YZmmQ@mail.gmail.com' \
    --to=lukas.bulwahn@gmail.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.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 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.