| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20251024103934.20019-3-bagasdotme@gmail.com> Date: Fri, 24 Oct 2025 17:39:34 +0700 From: Bagas Sanjaya <bagasdotme@...il.com> To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Documentation <linux-doc@...r.kernel.org>, Linux Input Devices <linux-input@...r.kernel.org> Cc: Jiri Kosina <jikos@...nel.org>, Benjamin Tissoires <bentiss@...nel.org>, Jonathan Corbet <corbet@....net>, Masaki Ota <masaki.ota@...alps.com>, George Anthony Vernon <contact@...rnon.com>, Bagas Sanjaya <bagasdotme@...il.com> Subject: [PATCH 2/2] Documentation: hid-alps: Format DataByte* subsection headings "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@...il.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
Powered by blists - more mailing lists