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>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Even Xu <even.xu@intel.com>, Chong Han <chong.han@intel.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH] HID: intel-thc-hid: Separate max input size control conditional list
Date: Fri, 13 Jun 2025 08:43:27 +0700 [thread overview]
Message-ID: <20250613014327.11514-1-bagasdotme@gmail.com> (raw)
Stephen Rothwell reports htmldocs warning:
Documentation/hid/intel-thc-hid.rst:200: ERROR: Unexpected indentation. [docutils]
Separate conditional list for max input size control by a blank line
to fix the warning.
Fixes: 45e92a093099 ("HID: Intel-thc-hid: Intel-thc: Introduce max input size control")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20250611142409.7d4683b0@canb.auug.org.au/
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/hid/intel-thc-hid.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/hid/intel-thc-hid.rst b/Documentation/hid/intel-thc-hid.rst
index 23d5110cb8710a..8b378c57b5aac0 100644
--- a/Documentation/hid/intel-thc-hid.rst
+++ b/Documentation/hid/intel-thc-hid.rst
@@ -195,6 +195,7 @@ This is a new feature introduced in Panther Lake platform, THC hardware allows d
a max input size for RxDMA. After this max size gets set and enabled, for every input report
packet reading, THC hardware sequencer will first read incoming input packet size, then compare
input packet size with the given max size:
+
- if input packet size <= max size, THC continues using input packet size to finish the reading
- if input packet size > max size, there is potential input data crash risk during
transferring, THC will use max size instead of input packet size for reading
base-commit: da04eb7791c461bc0f113ce96af4ed59bcc12555
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-06-13 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 1:43 Bagas Sanjaya [this message]
2025-06-13 3:07 ` [PATCH] HID: intel-thc-hid: Separate max input size control conditional list Xu, Even
2025-06-20 7:00 ` Jiri Kosina
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=20250613014327.11514-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bentiss@kernel.org \
--cc=chong.han@intel.com \
--cc=corbet@lwn.net \
--cc=even.xu@intel.com \
--cc=jikos@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).