From: Maud Spierings via B4 Relay <devnull+maud_spierings.hotmail.com@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-input@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Maud Spierings <maud_spierings@hotmail.com>
Subject: [PATCH] Input: docs: Fix the input_event struct documentation
Date: Sun, 10 Nov 2024 19:05:02 +0100 [thread overview]
Message-ID: <20241110-fix_input_doc-v1-1-745d5f908e61@hotmail.com> (raw)
From: Maud Spierings <maud_spierings@hotmail.com>
Fix the datatype of the value field of the input_event struct which is
signed instead of unsigned.
See include/uapi/linux/input.h
Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
---
Documentation/input/input.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/input/input.rst b/Documentation/input/input.rst
index 2c67fa904adcf902cebf8e7137c0a1609d879a50..d9a6de87d02de5301500b392191ab67e7db431ed 100644
--- a/Documentation/input/input.rst
+++ b/Documentation/input/input.rst
@@ -264,7 +264,7 @@ events on a read. Their layout is::
struct timeval time;
unsigned short type;
unsigned short code;
- unsigned int value;
+ int value;
};
``time`` is the timestamp, it returns the time at which the event happened.
---
base-commit: de2f378f2b771b39594c04695feee86476743a69
change-id: 20241110-fix_input_doc-1debf7bcd9c5
Best regards,
--
Maud Spierings <maud_spierings@hotmail.com>
next reply other threads:[~2024-11-10 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 18:05 Maud Spierings via B4 Relay [this message]
2024-11-27 20:04 ` [PATCH] Input: docs: Fix the input_event struct documentation Dmitry Torokhov
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=20241110-fix_input_doc-v1-1-745d5f908e61@hotmail.com \
--to=devnull+maud_spierings.hotmail.com@kernel.org \
--cc=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maud_spierings@hotmail.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).