From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <yi1.lai@intel.com>
Cc: Shahar Shitrit <shshitrit@nvidia.com>,
lkp@intel.com, netdev@vger.kernel.org,
Dragos Tatulea <dtatulea@nvidia.com>,
linux-kernel@vger.kernel.org, oe-lkp@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [linus:master] [net] 8e63c9e617: ltp.uevent02.fail
Date: Wed, 12 Aug 2026 11:55:54 +0200 [thread overview]
Message-ID: <anxDKg9rIbSzRS2e@yuki.lan> (raw)
In-Reply-To: <202608120846.30e0fb5b-lkp@intel.com>
Hi!
The test was asserting, among other things, the exact order of the
events and it expects:
Add ...net/ltp-tun
Add ...ltp-tun/queues/rx-0
Add ...ltp-tun/queues/tx-0
But after this patch the order changed to:
Add ...ltp-tun/queues/rx-0
Add ...ltp-tun/queues/tx-0
Add ...net/ltp-tun
Is the order of these messages guaranteed or do we need to adjust the
test?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <yi1.lai@intel.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
Shahar Shitrit <shshitrit@nvidia.com>,
lkp@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, oe-lkp@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [linus:master] [net] 8e63c9e617: ltp.uevent02.fail
Date: Wed, 12 Aug 2026 11:55:54 +0200 [thread overview]
Message-ID: <anxDKg9rIbSzRS2e@yuki.lan> (raw)
In-Reply-To: <202608120846.30e0fb5b-lkp@intel.com>
Hi!
The test was asserting, among other things, the exact order of the
events and it expects:
Add ...net/ltp-tun
Add ...ltp-tun/queues/rx-0
Add ...ltp-tun/queues/tx-0
But after this patch the order changed to:
Add ...ltp-tun/queues/rx-0
Add ...ltp-tun/queues/tx-0
Add ...net/ltp-tun
Is the order of these messages guaranteed or do we need to adjust the
test?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2026-08-12 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 6:54 [linus:master] [net] 8e63c9e617: ltp.uevent02.fail kernel test robot
2026-08-12 6:54 ` [LTP] " kernel test robot
2026-08-12 9:55 ` Cyril Hrubis [this message]
2026-08-12 9:55 ` Cyril Hrubis
2026-08-12 10:35 ` Dragos Tatulea
2026-08-12 10:35 ` Dragos Tatulea via ltp
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=anxDKg9rIbSzRS2e@yuki.lan \
--to=chrubis@suse.cz \
--cc=dtatulea@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=shshitrit@nvidia.com \
--cc=yi1.lai@intel.com \
/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.