From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Input Devices <linux-input@vger.kernel.org>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Masaki Ota <masaki.ota@jp.alps.com>,
George Anthony Vernon <contact@gvernon.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 2/2] Documentation: hid-alps: Format DataByte* subsection headings
Date: Fri, 24 Oct 2025 17:39:34 +0700 [thread overview]
Message-ID: <20251024103934.20019-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20251024103934.20019-1-bagasdotme@gmail.com>
"Command Read/Write" section has two DataByte* subsections describing
command bytes format. Add markup to these subsection heading texts.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/hid/hid-alps.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/hid/hid-alps.rst b/Documentation/hid/hid-alps.rst
index 3a22254e43464f..4a22a357f00c02 100644
--- a/Documentation/hid/hid-alps.rst
+++ b/Documentation/hid/hid-alps.rst
@@ -69,6 +69,7 @@ To read/write to RAM, need to send a command to the device.
The command format is as below.
DataByte(SET_REPORT)
+~~~~~~~~~~~~~~~~~~~~
===== ======================
Byte1 Command Byte
@@ -89,6 +90,7 @@ Value Byte is writing data when you send the write commands.
When you read RAM, there is no meaning.
DataByte(GET_REPORT)
+~~~~~~~~~~~~~~~~~~~~
===== ======================
Byte1 Response Byte
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-10-24 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 10:39 [PATCH 0/2] hid-alps docs heading cleanup Bagas Sanjaya
2025-10-24 10:39 ` [PATCH 1/2] Documentation: hid-alps: Fix packet format section headings Bagas Sanjaya
2025-10-24 10:39 ` Bagas Sanjaya [this message]
2025-10-25 7:12 ` [PATCH 0/2] hid-alps docs heading cleanup Randy Dunlap
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=20251024103934.20019-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bentiss@kernel.org \
--cc=contact@gvernon.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masaki.ota@jp.alps.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).