From: Zhangjin Wu <falcon@tinylab.org>
To: thomas@t-8ch.de, w@1wt.eu
Cc: falcon@tinylab.org, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: [PATCH v2 0/3] selftests/nolibc: add misc improvments
Date: Sat, 5 Aug 2023 14:09:57 +0800 [thread overview]
Message-ID: <cover.1691215074.git.falcon@tinylab.org> (raw)
Hi, Willy, Hi Thomas
Based on Thomas' suggestion, V2 comes here with relative path support
for O= option, v1 is [1].
// subdir
$ pwd
/labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc
$ mkdir -p out
$ make run-user O=out -C /labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/ -j4 | grep status
Makefile:122: srctree=/labs/linux-lab/src/linux-stable
Makefile:123: objtree: out
Makefile:124: COMMAND_O: O=/labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/out
Makefile:125: OUTPUT=/labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/out/
166 test(s): 158 passed, 8 skipped, 0 failed => status: warning
// topdir
$ pwd
/labs/linux-lab/src/linux-stable
$ mkdir -p out
$ make run-user O=out -C /labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/ -j4 | grep status
Makefile:122: srctree=/labs/linux-lab/src/linux-stable
Makefile:123: objtree: out
Makefile:124: COMMAND_O: O=/labs/linux-lab/src/linux-stable/out
Makefile:125: OUTPUT=/labs/linux-lab/src/linux-stable/out/
166 test(s): 158 passed, 8 skipped, 0 failed => status: warning
// outside
$ pwd
/labs/linux-lab/build
$ mkdir -p out
$ make run-user O=out -C /labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/ -j4 | grep status
Makefile:122: srctree=/labs/linux-lab/src/linux-stable
Makefile:123: objtree: out
Makefile:124: COMMAND_O: O=/labs/linux-lab/build/out
Makefile:125: OUTPUT=/labs/linux-lab/build/out/
166 test(s): 158 passed, 8 skipped, 0 failed => status: warning
Changes from v1 --> v2:
* selftests/nolibc: allow report with existing test log
tools/nolibc: stackprotector.h: make __stack_chk_init static
Add Reviewed-by line from Thomas
* selftests/nolibc: fix up O= option support
Now with relative path support with the help of $(COMMAND_O).
Suggested by Thomas.
Thanks!
Zhangjin
---
[1]: https://lore.kernel.org/lkml/cover.1691073180.git.falcon@tinylab.org/
Zhangjin Wu (3):
selftests/nolibc: allow report with existing test log
tools/nolibc: stackprotector.h: make __stack_chk_init static
selftests/nolibc: fix up O= option support
tools/include/nolibc/crt.h | 2 +-
tools/include/nolibc/stackprotector.h | 5 ++---
tools/testing/selftests/nolibc/Makefile | 19 +++++++++++++------
3 files changed, 16 insertions(+), 10 deletions(-)
--
2.25.1
next reply other threads:[~2023-08-05 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 6:09 Zhangjin Wu [this message]
2023-08-05 6:11 ` [PATCH v2 1/3] selftests/nolibc: allow report with existing test log Zhangjin Wu
2023-08-05 6:12 ` [PATCH v2 2/3] tools/nolibc: stackprotector.h: make __stack_chk_init static Zhangjin Wu
2023-08-05 6:13 ` [PATCH v2 3/3] selftests/nolibc: fix up O= option support Zhangjin Wu
2023-08-06 11:21 ` Willy Tarreau
2023-08-06 12:17 ` Zhangjin Wu
2023-08-26 4:30 ` Zhangjin Wu
2023-08-26 18:29 ` Yuan Tan
2023-08-27 7:09 ` Zhangjin Wu
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=cover.1691215074.git.falcon@tinylab.org \
--to=falcon@tinylab.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.de \
--cc=w@1wt.eu \
/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