From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: maud_spierings@hotmail.com
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-input@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: docs: Fix the input_event struct documentation
Date: Wed, 27 Nov 2024 12:04:12 -0800 [thread overview]
Message-ID: <Z0d7PHoI1FmeaI15@google.com> (raw)
In-Reply-To: <20241110-fix_input_doc-v1-1-745d5f908e61@hotmail.com>
On Sun, Nov 10, 2024 at 07:05:02PM +0100, Maud Spierings via B4 Relay wrote:
> 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>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2024-11-27 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 18:05 [PATCH] Input: docs: Fix the input_event struct documentation Maud Spierings via B4 Relay
2024-11-27 20:04 ` Dmitry Torokhov [this message]
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=Z0d7PHoI1FmeaI15@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=corbet@lwn.net \
--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).