From: "Jones, Michael-A1" <Michael-A1.Jones@analog.com>
To: Guenter Roeck <linux@roeck-us.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Jean Delvare <jdelvare@suse.com>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>
Subject: RE: [PATCH] docs: hmon: ltc2978.rst: fix a broken table
Date: Thu, 13 Feb 2020 16:38:26 +0000 [thread overview]
Message-ID: <SN6PR03MB40322F27BA88395ADD0BD5B8F61A0@SN6PR03MB4032.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20200213162403.GB16294@roeck-us.net>
-----Original Message-----
From: Guenter Roeck <groeck7@gmail.com> On Behalf Of Guenter Roeck
Sent: Thursday, February 13, 2020 9:24 AM
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>; Jonathan Corbet <corbet@lwn.net>; Jean Delvare <jdelvare@suse.com>; Jones, Michael-A1 <Michael-A1.Jones@analog.com>; linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] docs: hmon: ltc2978.rst: fix a broken table
[External]
On Thu, Feb 13, 2020 at 05:15:55PM +0100, Mauro Carvalho Chehab wrote:
> /devel/v4l/docs/Documentation/hwmon/ltc2978.rst:320: WARNING: Malformed table.
> Text in column margin in table line 80.
>
> Cc: Mike Jones <michael-a1.jones@analog.com>
> Fixes: 6d36d475215a ("hwmon: (pmbus/ltc2978) add support for more parts.")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Sorry, I may have messed that up when trying to fix lines exceeding
80 columns in that file. The problem is already fixed in -next.
MJ: I would like to know what tool produced the warning so I can run it next time before submission.
Guenter
next prev parent reply other threads:[~2020-02-13 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 16:15 [PATCH] docs: hmon: ltc2978.rst: fix a broken table Mauro Carvalho Chehab
2020-02-13 16:24 ` Guenter Roeck
2020-02-13 16:38 ` Jones, Michael-A1 [this message]
2020-02-13 16:52 ` Randy Dunlap
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=SN6PR03MB40322F27BA88395ADD0BD5B8F61A0@SN6PR03MB4032.namprd03.prod.outlook.com \
--to=michael-a1.jones@analog.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab+huawei@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).