From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, thomas@t-8ch.de
Subject: Re: [PATCH v4 00/18] selftests/nolibc: allow run with minimal kernel config
Date: Sun, 9 Jul 2023 11:41:54 +0200 [thread overview]
Message-ID: <20230709094154.GI9321@1wt.eu> (raw)
In-Reply-To: <cover.1688750763.git.falcon@tinylab.org>
Hi Zhangjin,
On Sat, Jul 08, 2023 at 02:21:20AM +0800, Zhangjin Wu wrote:
> This patchset assumes the chmod_net removal patchset will be applied at
> first, if not, the chmod_argv0 added alphabetically will not be applied.
> Since our new chmod_argv0 is exactly added to replace chmod_net, so,
> Willy, is it ok for you to at least apply the chmod_net removal patch
> [5] before this patchset?
Sure, and thanks for the reminder, I had missed it in the middle of
the flood.
(...)
> LOG: testing summary:
>
> arch/board | result
> ------------|------------
> arm/vexpress-a9 | 139 test(s) passed, 4 skipped, 0 failed.
> x86_64/pc | 139 test(s) passed, 4 skipped, 0 failed.
> mipsel/malta | 139 test(s) passed, 4 skipped, 0 failed.
> loongarch64/virt | 139 test(s) passed, 4 skipped, 0 failed.
Great, I like this, thank you! That was precisely the purpose of the
"skipped" initially, not to be too strictly bound to a specific config.
Now it's indeed even more flexible and that's better.
Series queued as well, thank you!
Willy
next prev parent reply other threads:[~2023-07-09 9:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 18:21 [PATCH v4 00/18] selftests/nolibc: allow run with minimal kernel config Zhangjin Wu
2023-07-07 18:22 ` [PATCH v4 01/18] selftests/nolibc: add run-libc-test target Zhangjin Wu
2023-07-07 18:23 ` [PATCH v4 02/18] selftests/nolibc: stat_fault: silence NULL argument warning with glibc Zhangjin Wu
2023-07-07 18:25 ` [PATCH v4 03/18] selftests/nolibc: gettid: restore for glibc and musl Zhangjin Wu
2023-07-07 18:26 ` [PATCH v4 04/18] selftests/nolibc: add _LARGEFILE64_SOURCE for musl Zhangjin Wu
2023-07-07 18:27 ` [PATCH v4 05/18] selftests/nolibc: fix up int_fast16/32_t test cases " Zhangjin Wu
2023-07-07 18:29 ` [PATCH v4 06/18] tools/nolibc: types.h: add RB_ flags for reboot() Zhangjin Wu
2023-07-07 18:30 ` [PATCH v4 07/18] selftests/nolibc: prefer <sys/reboot.h> to <linux/reboot.h> Zhangjin Wu
2023-07-07 18:32 ` [PATCH v4 08/18] selftests/nolibc: fix up kernel parameters support Zhangjin Wu
2023-07-07 18:33 ` [PATCH v4 09/18] selftests/nolibc: link_cross: use /proc/self/cmdline Zhangjin Wu
2023-07-07 18:34 ` [PATCH v4 10/18] tools/nolibc: add rmdir() support Zhangjin Wu
2023-07-07 18:35 ` [PATCH v4 11/18] selftests/nolibc: add a new rmdir() test case Zhangjin Wu
2023-07-07 18:37 ` [PATCH v4 12/18] selftests/nolibc: fix up failures when CONFIG_PROC_FS=n Zhangjin Wu
2023-07-07 18:38 ` [PATCH v4 13/18] selftests/nolibc: prepare /tmp for tmpfs or ramfs Zhangjin Wu
2023-07-09 9:38 ` Willy Tarreau
2023-07-10 5:06 ` Zhangjin Wu
2023-07-10 6:57 ` Willy Tarreau
2023-07-10 9:38 ` Zhangjin Wu
2023-07-07 18:40 ` [PATCH v4 14/18] selftests/nolibc: vfprintf: remove MEMFD_CREATE dependency Zhangjin Wu
2023-07-07 18:42 ` [PATCH v4 15/18] selftests/nolibc: chdir_root: restore current path after test Zhangjin Wu
2023-07-07 18:43 ` [PATCH v4 16/18] selftests/nolibc: stat_timestamps: remove procfs dependency Zhangjin Wu
2023-07-07 18:45 ` [PATCH v4 17/18] selftests/nolibc: chroot_exe: " Zhangjin Wu
2023-07-07 18:46 ` [PATCH v4 18/18] selftests/nolibc: add chmod_argv0 test Zhangjin Wu
2023-07-09 9:41 ` Willy Tarreau [this message]
2023-07-09 10:02 ` [PATCH v4 00/18] selftests/nolibc: allow run with minimal kernel config Willy Tarreau
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=20230709094154.GI9321@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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