From: Chris Packham <Chris.Packham@alliedtelesis•co.nz>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Guenter Roeck <linux@roeck-us•net>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the hwmon-staging tree
Date: Fri, 12 Mar 2021 04:00:45 +0000 [thread overview]
Message-ID: <27340bd8-2009-683d-ac44-b6bb51f4347e@alliedtelesis.co.nz> (raw)
In-Reply-To: <20210312145031.5df91293@canb.auug.org.au>
On 12/03/21 4:50 pm, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hwmon-staging tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/hwmon/ir36021.rst:34: WARNING: Malformed table.
> No bottom table border found.
>
> ======================= ===========================
> curr1_label "iin"
> curr1_input Measured input current
> curr1_alarm Input fault alarm
>
> curr2_label "iout1"
> curr2_input Measured output current
> curr2_alarm Output over-current alarm
>
> in1_label "vin"
> in1_input Measured input voltage
> in1_alarm Input under-voltage alarm
>
> in2_label "vout1"
> in2_input Measured output voltage
> in2_alarm Output over-voltage alarm
>
> power1_label "pin"
> power1_input Measured input power
> power1_alarm Input under-voltage alarm
>
> power2_label "pout1"
> power2_input Measured output power
>
> temp1_input Measured temperature
> temp1_alarm Temperature alarm
>
> temp2_input Measured other loop temperature
> temp2_alarm Temperature alarm
>
> Caused by commit
>
> 0be9fee30ff9 ("hwmon: (pmbus) Add driver for Infineon IR36021")
>
Easy enough to fix. Who should I send the patch to?
next prev parent reply other threads:[~2021-03-12 4:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 3:50 linux-next: build warning after merge of the hwmon-staging tree Stephen Rothwell
2021-03-12 4:00 ` Chris Packham [this message]
2021-03-12 4:45 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 4:54 Stephen Rothwell
2025-11-18 2:44 Stephen Rothwell
2025-11-19 5:25 ` Guenter Roeck
2025-09-08 8:07 Stephen Rothwell
2025-09-08 8:06 Stephen Rothwell
2025-03-18 10:35 Stephen Rothwell
2025-03-18 15:04 ` Guenter Roeck
2024-12-16 4:58 Stephen Rothwell
2024-03-26 5:03 Stephen Rothwell
2023-12-12 3:12 Stephen Rothwell
2023-12-12 5:11 ` Guenter Roeck
2023-10-30 5:15 Stephen Rothwell
2022-08-31 5:30 Stephen Rothwell
2022-05-10 10:11 Stephen Rothwell
2022-05-10 10:47 ` Zev Weiss
2022-05-10 14:03 ` Guenter Roeck
2022-05-03 7:22 Stephen Rothwell
2022-05-03 7:34 ` Michael Walle
2022-05-03 13:08 ` Guenter Roeck
2022-02-10 7:51 Stephen Rothwell
2022-02-10 8:50 ` Lee Jones
2022-02-10 17:33 ` Guenter Roeck
2022-02-10 18:07 ` Lee Jones
2022-02-10 18:22 ` Guenter Roeck
2022-02-04 5:16 Stephen Rothwell
2022-02-04 5:25 ` Guenter Roeck
2021-12-20 11:31 Stephen Rothwell
2021-12-20 0:00 Stephen Rothwell
2021-06-10 0:21 Stephen Rothwell
2021-06-10 3:38 ` Guenter Roeck
2021-03-30 7:27 Stephen Rothwell
2021-03-30 10:38 ` Guenter Roeck
2021-03-30 20:25 ` Chris Packham
2021-03-30 20:55 ` Guenter Roeck
2021-01-29 7:03 Stephen Rothwell
2020-12-07 7:51 Stephen Rothwell
2020-11-30 0:56 Stephen Rothwell
2020-11-30 1:14 ` Paul Barker
2020-11-30 14:53 ` Guenter Roeck
2020-02-10 22:23 Stephen Rothwell
2020-02-11 0:24 ` Guenter Roeck
2019-07-01 2:26 Stephen Rothwell
2019-06-06 0:34 Stephen Rothwell
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=27340bd8-2009-683d-ac44-b6bb51f4347e@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis$(echo .)co.nz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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