From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-arm-kernel@lists.infradead.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] lib: tst_fd: Add kernel version check to memfd_secret
Date: Fri, 21 Jun 2024 11:07:22 +0200 [thread overview]
Message-ID: <ZnVCyl5QUNdGu_NR@yuki> (raw)
In-Reply-To: <20240620132511.GA599458@pevik>
Hi!
Can we first try the simple solution by adding fallback definitions
before we add such complexity there?
--
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: Petr Vorel <pvorel@suse.cz>
Cc: nobuhiro1.iwamatsu@toshiba.co.jp, ltp@lists.linux.it,
linux-arm-kernel@lists.infradead.org
Subject: Re: [LTP] [PATCH] lib: tst_fd: Add kernel version check to memfd_secret
Date: Fri, 21 Jun 2024 11:07:22 +0200 [thread overview]
Message-ID: <ZnVCyl5QUNdGu_NR@yuki> (raw)
In-Reply-To: <20240620132511.GA599458@pevik>
Hi!
Can we first try the simple solution by adding fallback definitions
before we add such complexity there?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2024-06-21 9:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 8:49 [LTP] [PATCH] lib: tst_fd: Add kernel version check to memfd_secret Nobuhiro Iwamatsu
2024-06-18 10:15 ` Cyril Hrubis
2024-06-19 5:24 ` nobuhiro1.iwamatsu
2024-06-19 17:33 ` Petr Vorel
2024-06-19 17:33 ` Petr Vorel
2024-06-20 1:22 ` nobuhiro1.iwamatsu
2024-06-20 1:22 ` nobuhiro1.iwamatsu
2024-06-20 13:25 ` Petr Vorel
2024-06-20 13:25 ` Petr Vorel
2024-06-21 9:07 ` Cyril Hrubis [this message]
2024-06-21 9:07 ` Cyril Hrubis
2024-06-21 9:05 ` Cyril Hrubis
2024-06-21 11:09 ` Petr Vorel
2024-06-28 8:40 ` nobuhiro1.iwamatsu
2024-07-12 18:40 ` Edward Liaw via ltp
2024-07-16 4:25 ` nobuhiro1.iwamatsu
-- strict thread matches above, loose matches on Subject: below --
2024-06-18 9:09 Nobuhiro Iwamatsu
2024-06-21 11:13 ` Petr Vorel
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=ZnVCyl5QUNdGu_NR@yuki \
--to=chrubis@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ltp@lists.linux.it \
--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 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.