From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] Documentation: PCI: Documentation fixes for vNTB
Date: Wed, 22 Jun 2022 16:53:43 +0700 [thread overview]
Message-ID: <20220622095345.27121-1-bagasdotme@gmail.com> (raw)
In-Reply-To: <20220621200235.211b2e32@canb.auug.org.au>
After merging ntb tree for linux-next integration testing, Stephen
Rothwell reported following htmldocs warnings:
Documentation/PCI/endpoint/pci-vntb-function.rst:82: WARNING: Unexpected indentation.
Documentation/PCI/endpoint/pci-vntb-howto.rst:131: WARNING: Title underline too short.
These warnings are introduced by commit 0c4b285d9636cc ("Documentation: PCI:
Add specification for the PCI vNTB function device").
Fix these two warnings above by:
1. Using code block for scratchpad diagram ([1/2])
2. Extending "lspci output" subheading underline syntax ([2/2])
This patchset is based on next-20220622.
Bagas Sanjaya (2):
Documentation: PCI: Use code-block block for scratchpad registers
diagram
Documentation: PCI: extend subheading underline for "lspci output"
section
Documentation/PCI/endpoint/pci-vntb-function.rst | 5 ++++-
Documentation/PCI/endpoint/pci-vntb-howto.rst | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
base-commit: ac0ba5454ca85162c08dc429fef1999e077ca976
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-22 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 10:02 linux-next: build warning after merge of the ntb tree Stephen Rothwell
2022-06-22 9:53 ` Bagas Sanjaya [this message]
2022-06-22 9:53 ` [PATCH 1/2] Documentation: PCI: Use code-block block for scratchpad registers diagram Bagas Sanjaya
2022-06-23 15:37 ` [EXT] " Frank Li
2022-06-22 9:53 ` [PATCH 2/2] Documentation: PCI: extend subheading underline for "lspci output" section Bagas Sanjaya
2022-08-12 14:04 ` [PATCH 0/2] Documentation: PCI: Documentation fixes for vNTB Jon Mason
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=20220622095345.27121-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=linux-doc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.