From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Jonathan Corbet <corbet@lwn.net>,
Allison Randal <allison@lohutok.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: samsung-s3c24xx: Add blank line after SPDX directive
Date: Tue, 14 Jun 2022 15:49:40 +0700 [thread overview]
Message-ID: <22e6a8ff-ee1c-69c9-dbcf-2865142e05c1@gmail.com> (raw)
In-Reply-To: <20220614084658.509389-1-bagasdotme@gmail.com>
On 6/14/22 15:46, Bagas Sanjaya wrote:
> After merging spdx tree for linux-next testing, Stephen Rothwell reported
> htmldocs warning:
>
> Documentation/arm/samsung-s3c24xx/cpufreq.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
>
> It is due to missing blank line separator between SPDX directive and
> page title.
>
> Add the blank line to fix the warning.
>
> Link: https://lore.kernel.org/linux-next/20220614164506.6afd65a6@canb.auug.org.au/
> Fixes: b7bc1c9e5b04da ("treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_147.RULE")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Allison Randal <allison@lohutok.net>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
Oops, I forgot to mention that this patch is based on next-20220614.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-14 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220614164506.6afd65a6@canb.auug.org.au>
2022-06-14 8:46 ` [PATCH] Documentation: samsung-s3c24xx: Add blank line after SPDX directive Bagas Sanjaya
2022-06-14 8:49 ` Bagas Sanjaya [this message]
2022-06-27 2:43 ` Bagas Sanjaya
2022-06-27 7:32 ` Greg Kroah-Hartman
2022-06-27 7:44 ` Bagas Sanjaya
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=22e6a8ff-ee1c-69c9-dbcf-2865142e05c1@gmail.com \
--to=bagasdotme@gmail.com \
--cc=allison@lohutok.net \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).