From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] question about running input testcase
Date: Fri, 15 Apr 2016 18:02:48 +0800 [thread overview]
Message-ID: <5710BC48.9070106@cn.fujitsu.com> (raw)
In-Reply-To: <20160413094000.GA10941@rei.lan>
Hi Cyril
to 2016/04/13 17:40, Cyril Hrubis wrote:
> Hi!
> I'm afraid that cedric@suse.com no longer works as Cedric was here only
> for his internship. I can try to ask our kernel developers that he
> worked on these testcases with though.
>
I have runned these test cases in RHEL5.11GA and RHEL6.8Beta.
When above patch is not applied, input/04 and input/05 failed with the following messages.
-----------------------------------------------------------------------------------------
[root@linux6 input]# ./input04
input04 0 TINFO : Found uinput dev at /dev/uinput
input04 0 TINFO : Unexpected ev type=0 code=0 value=0
input04 1 TFAIL : input04.c:65: Data received /dev/inputX
[root@linux6 input]# ./input05
input05 0 TINFO : Found uinput dev at /dev/uinput
input05 0 TINFO : Unexpected ev type=0 code=0 value=0
input05 1 TFAIL : input05.c:69: Data received in eventX
When above patch is applied, input/04 and input/05 passed with the following messages.
-----------------------------------------------------------------------------------------
[root@linux6 input]# ./input04
input04 0 TINFO : Found uinput dev at /dev/uinput
input04 1 TPASS : No data received in /dev/inputX
[root@linux6 input]# ./input05
input05 0 TINFO : Found uinput dev at /dev/uinput
input05 1 TPASS : No data received in eventX
So, i think the above patch fixes this bug.
Regards,
Xiao Yang
next prev parent reply other threads:[~2016-04-15 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 7:05 [LTP] question about running input testcase Xiao Yang
2016-04-13 9:40 ` Cyril Hrubis
2016-04-14 1:42 ` Xiao Yang
2016-04-15 10:02 ` Xiao Yang [this message]
2016-05-26 8:54 ` Xiao Yang
2016-06-07 12:58 ` Cyril Hrubis
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=5710BC48.9070106@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--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.