From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Wake Liu" <wakel@google.com>
Cc: rbranco@suse.com, Wake Liu via ltp <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] lapi/userfaultfd: Handle ENOSYS in SAFE_USERFAULTFD
Date: Wed, 29 Apr 2026 10:02:33 +0000 [thread overview]
Message-ID: <69f1d73a.050a0220.3c19ab.a437@mx.google.com> (raw)
In-Reply-To: <CAOcRiAEQnOGn7X5U51Jr_dYGCc6mRYwL_Vh68FNtkvRXXrCh7g@mail.gmail.com>
> What do you think about this? I would be happy to send a v2 patch
> addressing this.
>
no everything makes more sense :-) the right way to handle this issue
is to use needs_kconfig as I explained in the first email.
Feel free to follow that pattern after trying it out. It should work.
Kind 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-04-29 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 6:40 [LTP] [PATCH] lapi/userfaultfd: Handle ENOSYS in SAFE_USERFAULTFD Wake Liu via ltp
2026-04-29 6:52 ` Andrea Cervesato via ltp
2026-04-29 8:51 ` Wake Liu via ltp
2026-04-29 9:22 ` Andrea Cervesato via ltp
2026-04-29 9:48 ` Wake Liu via ltp
2026-04-29 10:02 ` Andrea Cervesato via ltp [this message]
2026-04-29 10:12 ` [LTP] [PATCH] syscalls/userfaultfd04: Require CONFIG_USERFAULTFD=y Wake Liu via ltp
2026-04-29 12:22 ` [LTP] " linuxtestproject.agent
2026-05-06 15:52 ` [LTP] [PATCH] " Andrea Cervesato via ltp
2026-05-06 15:57 ` Andrea Cervesato via ltp
2026-04-29 7:31 ` [LTP] lapi/userfaultfd: Handle ENOSYS in SAFE_USERFAULTFD linuxtestproject.agent
2026-04-29 7:36 ` Andrea Cervesato via ltp
2026-04-29 11:07 ` [LTP] [PATCH] " 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=69f1d73a.050a0220.3c19ab.a437@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=rbranco@suse.com \
--cc=wakel@google.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.