linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the hwmon-staging tree
Date: Tue, 7 Jun 2022 16:37:07 +0700	[thread overview]
Message-ID: <Yp8cQ1BcDXuZ9Cv4@debian.me> (raw)
In-Reply-To: <20220607141958.1e31971d@canb.auug.org.au>

On Tue, Jun 07, 2022 at 02:19:58PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hwmon-staging tree, today's linux-next build (htmldocs)
> produced these warnings:
> 
> Documentation/hwmon/lt7182s.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
> Documentation/hwmon/lt7182s.rst:75: WARNING: Malformed table.
> Text in column margin in table line 33.
> 
> ======================  ====================================
> curr[1-2]_label         "iin[12]"
> curr[1-2]_input         Measured input current
> curr[1-2]_max           Maximum input current
> curr[1-2]_max_alarm     Current high alarm
> 
> curr[3-4]_label         "iout[1-2]"
> curr[3-4]_input         Measured output current
> curr[3-4]_highest       Highest measured output current
> curr[3-4]_max           Maximum output current
> curr[3-4]_max_alarm     Output current high alarm
> 
> in[1-2]_label           "vin[12]"
> in[1-2]_input           Measured input voltage
> in[1-2]_highest         Highest measured input voltage
> in[1-2]_crit            Critical maximum input voltage
> in[1-2]_crit_alarm      Input voltage critical high alarm
> in[1-2]_min             Minimum input voltage
> in[1-2]_min_alarm       Input voltage low alarm
> in[1-2]_rated_min       Rated minimum input voltage
> in[1-2]_rated_max       Rated maximum input voltage
> in1_reset_history       Write to reset history for all attributes
> 
> in[3-5]_label           "vmon[1-3]"
> in[3-5]_input           Measured voltage on ITH1/ITH2/EXTVCC pins
>                         Only available if enabled with MFR_ADC_CONTROL_LT7182S
>                         command.
> 
> in[3-4|6-7]_label       "vout[1-2]"
> in[3-4|6-7]_input       Measured output voltage
> in[3-4|6-7]_highest     Highest measured output voltage
> in[3-4|6-7]_lcrit       Critical minimum output voltage
> in[3-4|6-7]_lcrit_alarm Output voltage critical low alarm
> in[3-4|6-7]_min         Minimum output voltage
> in[3-4|6-7]_max_alarm   Output voltage low alarm
> in[3-4|6-7]_max         Maximum output voltage
> in[3-4|6-7]_max_alarm   Output voltage high alarm
> in[3-4|6-7]_crit        Critical maximum output voltage
> in[3-4|6-7]_crit_alarm  Output voltage critical high alarm
> 
> power[1-2]_label        "pout[1-2]"
> power[1-2]_input        Measured output power
> 
> temp1_input             Measured temperature
> temp1_crit              Critical high temperature
> temp1_crit_alarm        Chip temperature critical high alarm
> temp1_max               Maximum temperature
> temp1_max_alarm         Chip temperature high alarm
> ======================  ====================================
> 
> Introduced by commit
> 
>   3d6bcaa21fbd ("hwmon: (pmbus) Add support for Analog Devices LT7182S")
> 

Hi Stephen,

The warning above doesn't appear when doing htmldocs build using Sphinx
installed from pip on my system.

Cc-ing linux-doc list.

-- 
An old man doll... just what I always wanted! - Clara

       reply	other threads:[~2022-06-07  9:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220607141958.1e31971d@canb.auug.org.au>
2022-06-07  9:37 ` Bagas Sanjaya [this message]
2022-06-07 12:40   ` linux-next: build warnings after merge of the hwmon-staging tree Guenter Roeck
     [not found] <20220607142301.3eb8a53c@canb.auug.org.au>
2022-06-07  9:35 ` Bagas Sanjaya
2022-06-07 12:39   ` Guenter Roeck

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=Yp8cQ1BcDXuZ9Cv4@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).