From: Petr Vorel <pvorel@suse.cz>
To: "Kogure Akihisa ( 小暮 明久 )" <akihisa.kogure.ke@kyocera.jp>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] input_helper: Modify the check range of the input event number
Date: Thu, 28 Mar 2024 11:42:26 +0100 [thread overview]
Message-ID: <20240328104226.GA51940@pevik> (raw)
In-Reply-To: <OS0PR01MB6033D024FBB112A98DC3104AD9342@OS0PR01MB6033.jpnprd01.prod.outlook.com>
Hi,
> If the input event number is greater than 32, the newly added event ID
> will be 256 or later.
> When there were already 32 input events in the device, this test program
> only checked 0~99, so it failed because it could not find a new input
> event ID.
> In order to eliminate this failure, we changed the event ID range to be
> checked by this test program to 0~1023.
> (https://github.com/torvalds/linux/commit/7f8d4cad1e4e11a45d02bd6e024cc2812963c38a, it looks like the upper limit should be 1023.)
For 1024:
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Ideally you would send v2, but we can also update the commit message and code
before merge.
Kind regards,
Petr
> ---
> diff --git a/testcases/kernel/input/input_helper.c b/testcases/kernel/input/input_helper.c
> index 09530fb..6b60d17 100644
> --- a/testcases/kernel/input/input_helper.c
> +++ b/testcases/kernel/input/input_helper.c
> @@ -40,7 +40,7 @@
> int ret, fd = -1;
> unsigned int i;
> - for (i = 0; i < 100; i++) {
> + for (i = 0; i < 1024; i++) {
> snprintf(path, sizeof(path), "/dev/input/event%i", i);
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-03-28 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 0:24 [LTP] [PATCH] input_helper: Modify the check range of the input event number Kogure Akihisa ( 小暮 明久 )
2024-03-26 14:23 ` Cyril Hrubis
2024-03-26 14:37 ` Cyril Hrubis
2024-03-27 1:26 ` Kogure Akihisa ( 小暮 明久 )
2024-03-28 10:42 ` Petr Vorel [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=20240328104226.GA51940@pevik \
--to=pvorel@suse.cz \
--cc=akihisa.kogure.ke@kyocera.jp \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.