From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Martin Cermak" <mcermak@redhat.com>
Cc: valgrind-developers@lists.sourceforge.net,
Martin Cermak via ltp <ltp@lists.linux.it>
Subject: Re: [LTP] [Valgrind-developers] [PATCH] Make userfaultfd0{1, 3, 4} LTP tests valgrind compatible
Date: Tue, 28 Apr 2026 08:55:32 +0000 [thread overview]
Message-ID: <69f07607.050a0220.38134b.31b1@mx.google.com> (raw)
In-Reply-To: <20260428085121.qeeka7axie3rervl@lida.tpb.lab.eng.brq.redhat.com>
> Hi Andrea,
>
> the patch is below. It adds 6 new tests. New tests are easy to
> text-diff against their originals. The only difference is that
> new tests use fork() or clone() instead of threads to handle the
> page fault. Please review:
I seen it, but when we receive patches as comments to the original
patches (without versioning), we get out of the loop of CI + automatic
review, which is our bare minimum request in order to accept patches
from LTP ML.
Kind Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-04-28 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 15:23 [LTP] [PATCH] Make userfaultfd0{1, 3, 4} LTP tests valgrind compatible Martin Cermak via ltp
2026-04-21 17:06 ` [LTP] " linuxtestproject.agent
2026-04-22 5:37 ` [LTP] [Valgrind-developers] [PATCH] " Petr Vorel
2026-04-22 7:54 ` Ricardo Branco
2026-04-22 12:17 ` Petr Vorel
2026-04-22 12:42 ` Ricardo Branco
2026-04-22 13:08 ` Martin Cermak via ltp
2026-04-23 14:44 ` Martin Cermak via ltp
2026-04-28 8:35 ` Andrea Cervesato via ltp
2026-04-28 8:51 ` Martin Cermak via ltp
2026-04-28 8:55 ` Andrea Cervesato via ltp [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=69f07607.050a0220.38134b.31b1@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=mcermak@redhat.com \
--cc=valgrind-developers@lists.sourceforge.net \
/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.