linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Alistair Francis <alistair@alistair23.me>,
	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: Thu, 10 Feb 2022 08:50:03 +0000	[thread overview]
Message-ID: <YgTRu7iLgJMymeT5@google.com> (raw)
In-Reply-To: <20220210185123.4d39766c@canb.auug.org.au>

On Thu, 10 Feb 2022, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the hwmon-staging tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/hwmon/sy7636a-hwmon.rst:4: WARNING: Title underline too short.
> 
> Kernel driver sy7636a-hwmon
> =========================
> 
> Introduced by commit
> 
>   de34a4053250 ("hwmon: sy7636a: Add temperature driver for sy7636a")

Oh wow, that's new (to me), and a little petty, no?

Would you like me to apply this patch to my branch Guenter?

I can either send out a new PR, or let it wallow.

-------- 8< --------

From: Lee Jones <lee.jones@linaro.org>

 Documentation/hwmon/sy7636a-hwmon.rst:4: WARNING: Title underline too short.

 Kernel driver sy7636a-hwmon
 =========================

Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
 Documentation/hwmon/sy7636a-hwmon.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/hwmon/sy7636a-hwmon.rst b/Documentation/hwmon/sy7636a-hwmon.rst
index 5612079397d52..c85db7b329415 100644
--- a/Documentation/hwmon/sy7636a-hwmon.rst
+++ b/Documentation/hwmon/sy7636a-hwmon.rst
@@ -1,7 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0-or-later
 
 Kernel driver sy7636a-hwmon
-=========================
+===========================
 
 Supported chips:
 
-- 

Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2022-02-10  8:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  7:51 linux-next: build warning after merge of the hwmon-staging tree Stephen Rothwell
2022-02-10  8:50 ` Lee Jones [this message]
2022-02-10 17:33   ` Guenter Roeck
2022-02-10 18:07     ` Lee Jones
2022-02-10 18:22       ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
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-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-03-12  3:50 Stephen Rothwell
2021-03-12  4:00 ` Chris Packham
2021-03-12  4:45   ` Stephen Rothwell
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=YgTRu7iLgJMymeT5@google.com \
    --to=lee.jones@linaro.org \
    --cc=alistair@alistair23.me \
    --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).