From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] userfaultfd: Minor fixes
Date: Thu, 26 Mar 2026 12:43:27 +0000 [thread overview]
Message-ID: <69c529ef.050a0220.2ab184.8fc8@mx.google.com> (raw)
In-Reply-To: <20260326123255.GB152048@pevik>
> Yes, IMHO TFAIL.
>
I guess we need to agree on the solution here, otherwise Ricard will be
puzzled :-)
I see TBROK as the right solution, since TFAIL should be used on the subject of
our tests. Also, if we receive the wrong event there's no purpose to continue
with the test because that means we have a kernel bug.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-26 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 15:47 [LTP] [PATCH v2] userfaultfd: Minor fixes Ricardo Branco
2026-03-26 8:38 ` Andrea Cervesato via ltp
2026-03-26 11:37 ` Ricardo Branco
2026-03-26 12:32 ` Petr Vorel
2026-03-26 12:43 ` Andrea Cervesato via ltp [this message]
2026-03-26 13:12 ` Petr Vorel
2026-03-26 12:38 ` Andrea Cervesato 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=69c529ef.050a0220.2ab184.8fc8@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=pvorel@suse.cz \
/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