linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Adam Zerella <adam.zerella@gmail.com>
Cc: jdelvare@suse.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: hwmon: Suppress Sphinx warning
Date: Sun, 15 Sep 2019 04:07:38 -0600	[thread overview]
Message-ID: <20190915040738.586cf00f@lwn.net> (raw)
In-Reply-To: <20190915082718.3590-1-adam.zerella@gmail.com>

On Sun, 15 Sep 2019 18:27:18 +1000
Adam Zerella <adam.zerella@gmail.com> wrote:

> When generating documentation output Sphinx
> outputs a warning for not including
> the page 'inspur-ipsps1.rst' in 'index.rst'.
> Assuming this documentation is useful it
> should be included in the index
> 
> Signed-off-by: Adam Zerella <adam.zerella@gmail.com>

Thanks for working to improve the docs!  A couple of quick notes...

 - "suppress a warning" is not a particularly helpful subject line.
   Something like "include inspur-ipsps1.rst in the docs build" says a
   lot more about what you're actually doing.

>  Documentation/hwmon/index.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/hwmon/index.rst b/Documentation/hwmon/index.rst
> index 8147c3f218bf..230ad59b462b 100644
> --- a/Documentation/hwmon/index.rst
> +++ b/Documentation/hwmon/index.rst
> @@ -7,6 +7,7 @@ Linux Hardware Monitoring
>  
>     hwmon-kernel-api
>     pmbus-core
> +   inspur-ipsps1

 - Which tree is this against?  I don't even have that file, and mainline
   doesn't either.  If this is in linux-next, the fix should probably go
   in via the same tree.

>     submitting-patches
>     sysfs-interface
>     userspace-tools

Thanks,

jon

  reply	other threads:[~2019-09-15 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15  8:27 [PATCH] docs: hwmon: Suppress Sphinx warning Adam Zerella
2019-09-15 10:07 ` Jonathan Corbet [this message]
2019-09-16  8:25 ` Jean Delvare

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=20190915040738.586cf00f@lwn.net \
    --to=corbet@lwn.net \
    --cc=adam.zerella@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).