From: Dave Jiang <dave.jiang@intel.com>
To: alison.schofield@intel.com, Vishal Verma <vishal.l.verma@intel.com>
Cc: nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org
Subject: Re: [ndctl PATCH] cxl/documentation: tidy up cxl-wait-sanitize man page format
Date: Thu, 29 Feb 2024 15:11:16 -0700 [thread overview]
Message-ID: <519a99b6-9bc9-4e2e-8eef-46f571efb6cc@intel.com> (raw)
In-Reply-To: <20240229212838.2006205-1-alison.schofield@intel.com>
On 2/29/24 2:28 PM, alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> Remove extra '==' to address these asciidoctor complaints:
>
> Generating Documentation/cxl/cxl-wait-sanitize with a custom command
> ERROR: cxl-wait-sanitize.txt: line 1: non-conforming manpage title
> ERROR: cxl-wait-sanitize.txt: line 3: name section expected
> WARNING: cxl-wait-sanitize.txt: line 4: unterminated example block
> WARNING: cxl-wait-sanitize.txt: line 26: unterminated listing block
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/cxl/cxl-wait-sanitize.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/cxl/cxl-wait-sanitize.txt b/Documentation/cxl/cxl-wait-sanitize.txt
> index 9047b74f0716..e8f2044e4882 100644
> --- a/Documentation/cxl/cxl-wait-sanitize.txt
> +++ b/Documentation/cxl/cxl-wait-sanitize.txt
> @@ -1,7 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
>
> cxl-wait-sanitize(1)
> -======================
> +====================
>
> NAME
> ----
>
> base-commit: 4d767c0c9b91d254e8ff0d7f0d3be04a498ad9f0
prev parent reply other threads:[~2024-02-29 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 21:28 [ndctl PATCH] cxl/documentation: tidy up cxl-wait-sanitize man page format alison.schofield
2024-02-29 22:11 ` Dave Jiang [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=519a99b6-9bc9-4e2e-8eef-46f571efb6cc@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).