From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Nitin Joshi <njoshi1@lenovo.com>,
Sugumaran <slacshiminar@lenovo.com>,
Bastien Nocera <bnocera@redhat.com>,
Mark Pearson <markpearson@lenovo.com>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Documentation: laptops: thinkpad-acpi: fix underline length build warning
Date: Mon, 24 Aug 2020 16:10:33 -0600 [thread overview]
Message-ID: <20200824161033.0448f327@lwn.net> (raw)
In-Reply-To: <7b2ecef9-dfb7-808a-7c05-4e4f44b363c4@infradead.org>
On Sun, 23 Aug 2020 15:55:16 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix underline length build warning in thinkpad-acpi.rst documentation:
>
> Documentation/admin-guide/laptops/thinkpad-acpi.rst:1437: WARNING: Title underline too short.
> DYTC Lapmode sensor
> ------------------
>
> Fixes: acf7f4a59114 ("platform/x86: thinkpad_acpi: lap or desk mode interface")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Nitin Joshi <njoshi1@lenovo.com>
> Cc: Sugumaran <slacshiminar@lenovo.com>
> Cc: Bastien Nocera <bnocera@redhat.com>
> Cc: Mark Pearson <markpearson@lenovo.com>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Darren Hart <dvhart@infradead.org>
> Cc: Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>
> Cc: ibm-acpi-devel@lists.sourceforge.net
> Cc: platform-driver-x86@vger.kernel.org
> ---
> Documentation/admin-guide/laptops/thinkpad-acpi.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
jon
prev parent reply other threads:[~2020-08-24 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 22:55 Randy Dunlap
2020-08-24 22:10 ` Jonathan Corbet [this message]
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=20200824161033.0448f327@lwn.net \
--to=corbet@lwn.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bnocera@redhat.com \
--cc=dvhart@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markpearson@lenovo.com \
--cc=njoshi1@lenovo.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=slacshiminar@lenovo.com \
/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
all inboxes | Powered by JetHome®