($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Kogure Akihisa ( 小暮 明久 )" <akihisa.kogure.ke@kyocera.jp>
To: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: [LTP] [PATCH] input_helper: Modify the check range of the input event number
Date: Tue, 26 Mar 2024 00:24:19 +0000	[thread overview]
Message-ID: <TYAPR01MB6044D2E0749663D84DE1F395D9352@TYAPR01MB6044.jpnprd01.prod.outlook.com> (raw)

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~356 (256+100).

Bug: 330269984
Test: ltp
Change-Id: I1b53008b15641fcdccf214af9183de1c29a3309c
---

diff --git a/testcases/kernel/input/input_helper.c b/testcases/kernel/input/input_helper.c
index c929de6..f086ae5 100644
--- a/testcases/kernel/input/input_helper.c
+++ b/testcases/kernel/input/input_helper.c
@@ -41,7 +41,7 @@
      int ret, fd = -1;
      unsigned int i;

-     for (i = 0; i < 100; i++) {
+     for (i = 0; i < 356; i++) {
            snprintf(path, sizeof(path), "/dev/input/event%i", i);

            fd = open(path, O_RDONLY);


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2024-03-26  0:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  0:24 Kogure Akihisa ( 小暮 明久 ) [this message]
2024-03-26 14:23 ` [LTP] [PATCH] input_helper: Modify the check range of the input event number Cyril Hrubis
2024-03-26 14:37   ` Cyril Hrubis
2024-03-27  1:26     ` Kogure Akihisa ( 小暮 明久 )
2024-03-28 10:42       ` Petr Vorel

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=TYAPR01MB6044D2E0749663D84DE1F395D9352@TYAPR01MB6044.jpnprd01.prod.outlook.com \
    --to=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 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 read-only IMAP folder(s) and NNTP newsgroup(s).