From: David Hildenbrand <david@redhat.com>
To: Petr Vorel <pvorel@suse.cz>, Martin Doucha <mdoucha@suse.cz>,
ltp@lists.linux.it, Cyril Hrubis <chrubis@suse.cz>
Subject: Re: [LTP] [PATCH v1 0/3] userfaultfd: Fix and remove compile-time TCONF handling
Date: Tue, 29 Nov 2022 09:46:59 +0100 [thread overview]
Message-ID: <3bcde8dc-cf2d-5881-33c6-b91b58681e60@redhat.com> (raw)
In-Reply-To: <Y4XC5sBLL8z8gviA@pevik>
>> I can just add to commit message of the first commit the reason Martin reported:
>> ppc64le on kernel 5.14 does not seem to support userfaultfd minor fault.
>
> In the end I merged without any change in commit message. You described the
> reason (runtime check) enough in the second commit. I was wrongly looking at
> fist commit, sorry for bothering you.
>
> Thank you both!
Thanks all!
--
Thanks,
David / dhildenb
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-11-29 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:18 [LTP] [PATCH v1 0/3] userfaultfd: Fix and remove compile-time TCONF handling David Hildenbrand
2022-11-28 11:18 ` [LTP] [PATCH v1 1/3] lapi/userfaultfd.h: Preparation for removing compile-time TCONF handling from userfaultfd testcases David Hildenbrand
2022-11-28 11:18 ` [LTP] [PATCH v1 2/3] security/dirtyc0w_shmem: Fix compile-time absence of UFFD_FEATURE_MINOR_SHMEM David Hildenbrand
2022-11-28 11:18 ` [LTP] [PATCH v1 3/3] syscalls/userfaultfd01: Remove compile-time TCONF handling David Hildenbrand
2022-11-28 11:57 ` [LTP] [PATCH v1 0/3] userfaultfd: Fix and remove " Petr Vorel
2022-11-28 12:29 ` Martin Doucha
2022-11-28 15:44 ` David Hildenbrand
2022-11-28 18:42 ` Petr Vorel
2022-11-29 8:29 ` Petr Vorel
2022-11-29 8:46 ` David Hildenbrand [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=3bcde8dc-cf2d-5881-33c6-b91b58681e60@redhat.com \
--to=david@redhat.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
--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