From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Akshay Gupta <akshay.gupta@amd.com>,
Srujana Challa <schalla@marvell.com>,
Vamsi Attunuru <vattunuru@marvell.com>,
Julien Panis <jpanis@baylibre.com>
Subject: [PATCH 0/3] misc devices formatting devices
Date: Tue, 4 Nov 2025 11:18:09 +0700 [thread overview]
Message-ID: <20251104041812.31402-1-bagasdotme@gmail.com> (raw)
Hi,
Here is a small docs formatting cleanup for assorted miscellaneous devices.
Patches [2-3/3] are split from my previous macro references fixup patch [1].
Enjoy!
[1]: https://lore.kernel.org/linux-doc/20251104022242.19224-1-bagasdotme@gmail.com/
Bagas Sanjaya (3):
Documentation: amd-sbi: Wrap miscdevice listing snippet in literal
code block
Documentation: mrvl-cn10k-dpi: Fix macro cross-reference syntax
Documentation: tps6594-pfsm: Fix macro cross-reference syntax
Documentation/misc-devices/amd-sbi.rst | 6 ++++--
Documentation/misc-devices/mrvl_cn10k_dpi.rst | 4 ++--
Documentation/misc-devices/tps6594-pfsm.rst | 12 ++++++------
3 files changed, 12 insertions(+), 10 deletions(-)
base-commit: 27600b51fbc8b9a4eba18c8d88d7edb146605f3f
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-11-04 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 4:18 Bagas Sanjaya [this message]
2025-11-04 4:18 ` [PATCH 1/3] Documentation: amd-sbi: Wrap miscdevice listing snippet in literal code block Bagas Sanjaya
2025-11-04 4:18 ` [PATCH 2/3] Documentation: mrvl-cn10k-dpi: Fix macro cross-reference syntax Bagas Sanjaya
2025-11-04 4:18 ` [PATCH 3/3] Documentation: tps6594-pfsm: " Bagas Sanjaya
2025-11-07 6:41 ` [PATCH 0/3] misc devices formatting devices Randy Dunlap
2025-11-10 19:56 ` Jonathan Corbet
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=20251104041812.31402-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akshay.gupta@amd.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jpanis@baylibre.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=schalla@marvell.com \
--cc=vattunuru@marvell.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 NNTP newsgroup(s).