From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Colin Ian King <colin.i.king@gmail.com>,
linux-gpio@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH ?next?] gpio: sim: add doc file to index file
Date: Sat, 22 Jan 2022 23:38:03 -0800 [thread overview]
Message-ID: <44959d7e-a930-cd5a-1113-b5bfc6da7782@infradead.org> (raw)
In-Reply-To: <20220123073536.12193-1-rdunlap@infradead.org>
Oops. Yes, the subject should say: [PATCH -next].
Sorry about that.
On 1/22/22 23:35, Randy Dunlap wrote:
> Include the gpio-sim.rst file in the GPIO index (toc/table of contents).
>
> Quietens this doc build warning:
>
> Documentation/admin-guide/gpio/gpio-sim.rst: WARNING: document isn't included in any toctree
>
> Fixes: b48f6b466e44 ("gpio: sim: new testing module")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> Documentation/admin-guide/gpio/index.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20220121.orig/Documentation/admin-guide/gpio/index.rst
> +++ linux-next-20220121/Documentation/admin-guide/gpio/index.rst
> @@ -10,6 +10,7 @@ gpio
> gpio-aggregator
> sysfs
> gpio-mockup
> + gpio-sim
>
> .. only:: subproject and html
>
--
~Randy
next prev parent reply other threads:[~2022-01-23 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 7:35 Randy Dunlap
2022-01-23 7:38 ` Randy Dunlap [this message]
2022-01-24 8:21 ` Bartosz Golaszewski
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=44959d7e-a930-cd5a-1113-b5bfc6da7782@infradead.org \
--to=rdunlap@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=colin.i.king@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®