All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH RFC 3/3] docs: add documentation for checkpatch
Date: Sun, 24 Jan 2021 22:16:58 +0530	[thread overview]
Message-ID: <CABJPP5BegcYznJ0wTBDoUg2b+wKeVrUxMnCQLowbOjMBDZkztQ@mail.gmail.com> (raw)
In-Reply-To: <CAKXUXMyCU=QLtoXAtvzsa4WjU0Pnw4iezcgja9bSPZJyEPa5qA@mail.gmail.com>

On Sun, Jan 24, 2021 at 10:08 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> On Sun, Jan 24, 2021 at 4:19 PM Dwaipayan Ray <dwaipayanray1@gmail.com> wrote:
> >
> > Link the tools directory to the document root for Sphinx.
> >
>
> Sorry, I did not mean "Documentation/tools/checkpatch.rst"
> _literally_; I only remembered that there is a subdirectory for
> "tools" in Documentation; and quickly wrote the mail without checking
> the actual name of the directory... assuming you would find the
> directory I meant.
>

Oh my bad! I actually searched for a while for a directory which contained
the scripts documentations actually and this totally slipped through my eyes.

I will correct the linkage.

> The directory is called "Documentation/dev-tools", it already has an
> index file and the checkpatch.pl documentation fits nicely there.
>
> Luksa
>
> > Signed-off-by: Dwaipayan Ray <dwaipayanray1@gmail.com>
> > ---
> >  Documentation/index.rst | 11 +++++++++++
> >  1 file changed, 11 insertions(+)
> >
> > diff --git a/Documentation/index.rst b/Documentation/index.rst
> > index 5888e8a7272f..ddd30e08a440 100644
> > --- a/Documentation/index.rst
> > +++ b/Documentation/index.rst
> > @@ -182,6 +182,17 @@ subprojects.
> >
> >     filesystems/ext4/index
> >
> > +Tools Documentation
> > +-------------------
> > +
> > +The documentation in this section provides details about the kernel tools
> > +and scripts.
> > +
> > +.. toctree::
> > +   :maxdepth: 2
> > +
> > +   tools/index
> > +
> >  Other documentation
> >  -------------------
> >
> > --
> > 2.30.0
> >
_______________________________________________
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:47 UTC|newest]

Thread overview: 14+ 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 [this message]
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
2021-01-24 16:51 ` Lukas Bulwahn
2021-01-26 18:35 [PATCH RFC 0/3] checkpatch: add verbose mode Dwaipayan Ray
2021-01-26 18:35 ` [Linux-kernel-mentees] [PATCH RFC 3/3] docs: add documentation for checkpatch Dwaipayan Ray

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=CABJPP5BegcYznJ0wTBDoUg2b+wKeVrUxMnCQLowbOjMBDZkztQ@mail.gmail.com \
    --to=dwaipayanray1@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=lukas.bulwahn@gmail.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.