From: Bagas Sanjaya <bagasdotme@gmail.com>
To: David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
Sadiya Kazi <sadiyakazi@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Daniel Latypov <dlatypov@google.com>, Rae Moar <rmoar@google.com>,
linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: kunit: Fix "How Do I Use This" / "Next Steps" sections
Date: Wed, 30 Nov 2022 15:18:02 +0700 [thread overview]
Message-ID: <cfa439e1-e216-8285-8283-1664453ac337@gmail.com> (raw)
In-Reply-To: <20221129094732.306449-1-davidgow@google.com>
On 11/29/22 16:47, David Gow wrote:
> The 'index' and 'start' pages end with very similar "How Do I Use This"
> / "Next Steps" sections respectively, which link to the other
> documentation pages. This wasn't updated when the tips.rst page was
> removed.
>
> Remove the reference to tips.rst, as well as tidy up the descriptions on
> all of the links (especially given that sphinx gives the page titles
> anyway.
>
While this patch is LGTM, what about simply drop these sections and
replace with "see the sidebar for other KUnit documentations"?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-11-30 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 9:47 [PATCH] Documentation: kunit: Fix "How Do I Use This" / "Next Steps" sections David Gow
2022-11-30 4:45 ` Sadiya Kazi
2022-11-30 8:18 ` Bagas Sanjaya [this message]
2022-12-01 20:48 ` Rae Moar
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=cfa439e1-e216-8285-8283-1664453ac337@gmail.com \
--to=bagasdotme@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
--cc=sadiyakazi@google.com \
--cc=skhan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox