From: Benjamin Tissoires <bentiss@kernel.org>
To: Jiri Kosina <jikos@kernel.org>,
Peter Hutterer <peter.hutterer@who-t.net>,
Shuah Khan <shuah@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] selftests/hid: upgrade the python scripts to match hid-tools 0.10
Date: Thu, 10 Jul 2025 16:21:11 +0200 [thread overview]
Message-ID: <175215727176.770911.16764304017186964894.b4-ty@kernel.org> (raw)
In-Reply-To: <20250709-wip-fix-ci-v1-0-b7df4c271cf8@kernel.org>
On Wed, 09 Jul 2025 11:08:48 +0200, Benjamin Tissoires wrote:
> hid-tools 0.10 fixed a test regression introduced in 6.16-rc1: the
> kernel might communicate with the uhid node while the test suite opens
> the evdev node. This leads to a full test-suite time which used to run
> in 6 minutes into an hour.
>
> Merge the upstream hid-tools project in the selftest kernel dir to
> reduce that time to something manageable again.
>
> [...]
Applied to hid/hid.git (for-6.17/selftests), thanks!
[1/3] selftests/hid: run ruff format on the python part
https://git.kernel.org/hid/hid/c/c85a8cb9b8d3
[2/3] selftests/hid: sync the python tests to hid-tools 0.8
https://git.kernel.org/hid/hid/c/642f9b2d608c
[3/3] selftests/hid: sync python tests to hid-tools 0.10
https://git.kernel.org/hid/hid/c/1aee3a44fad2
Cheers,
--
Benjamin Tissoires <bentiss@kernel.org>
prev parent reply other threads:[~2025-07-10 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 9:08 Benjamin Tissoires
2025-07-09 9:08 ` [PATCH 1/3] selftests/hid: run ruff format on the python part Benjamin Tissoires
2025-07-09 9:08 ` [PATCH 2/3] selftests/hid: sync the python tests to hid-tools 0.8 Benjamin Tissoires
2025-07-10 2:58 ` Peter Hutterer
2025-07-09 9:08 ` [PATCH 3/3] selftests/hid: sync python tests to hid-tools 0.10 Benjamin Tissoires
2025-07-10 14:21 ` Benjamin Tissoires [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=175215727176.770911.16764304017186964894.b4-ty@kernel.org \
--to=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®