All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] input: add kernel version check
Date: Fri, 18 Mar 2016 17:18:34 +0800	[thread overview]
Message-ID: <56EBC7EA.1000703@cn.fujitsu.com> (raw)
In-Reply-To: <20160222111826.GA5704@rei.lan>

于 2016/02/22 19:18, Cyril Hrubis 写道:
> Hi!
>> In this test case, the functionality of input has been improved by
>> following patch:
>> 'commit 4369c64c79a2 ("Input: Send events one packet at a time")'.
>> So it's not appropriate for testing on kernels that are lower than
>> 3.7.0 anymore.
> Are you sure that you have pointed out right commit? The commit
> description does not seem relevant.
>
> Also can you please describe why the testcases fail before 3.7.0 and
> how? Does kernel send empty sync events?
>
Hi!
When we run input04 on RHEL 5.11GA and 6.7GA, it still fails. It gives 
error message like this:

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

This failure is because kernel sends empty events. i.e
If we only send EV_SYN to input device, nothing should be received in 
/dev/input/eventX.
Actually, data is received in /dev/input/eventX. This investigation 
shows that it may be
improved by following patch:
'commit 4369c64c79a2 ("Input: Send events one packet at a time")'.

Do you think so ?

Regards,
Xiao Yang





  parent reply	other threads:[~2016-03-18  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19  9:38 [LTP] [PATCH] input: add kernel version check Xiao Yang
2016-02-22 11:18 ` Cyril Hrubis
2016-02-23  9:50   ` Xiao Yang
2016-03-18  9:18   ` Xiao Yang [this message]
2016-03-31 18:13     ` 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=56EBC7EA.1000703@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.