linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Zhangjin Wu <falcon@tinylab.org>
To: w@1wt.eu
Cc: arnd@arndb.de, falcon@tinylab.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
	thomas@t-8ch.de
Subject: [PATCH v2 0/7] nolibc: add generic part1 of prepare for rv32
Date: Mon, 29 May 2023 20:52:24 +0800	[thread overview]
Message-ID: <cover.1685362482.git.falcon@tinylab.org> (raw)

Hi, All

Thanks very much for your review suggestions of the v1 series [1], this
is the generic part1 of the v2 revison.

* selftests/nolibc: syscall_args: use generic __NR_statx

    A more generic statx is used instead of fstat

    (Review suggestions from Willy, Arnd)

* selftests/nolibc: allow specify extra arguments for qemu

    Besides BIOS, QEMU_ARGS_EXTRA is better for more requirements

    (Review suggestions from Thomas, Willy)

* selftests/nolibc: fix up compile warning with glibc on x86_64

    Definition of uint64_t differs from glibc and nolibc, use the right
    print format here

* selftests/nolibc: not include limits.h for nolibc

    Remove the requirement of limits.h for nolibc can let us use older
    glibc for rv32

    (Review suggestions from thomas)

* selftests/nolibc: use INT_MAX instead of __INT_MAX__

    A trivial cleanup, based on the previous patch

* tools/nolibc: arm: add missing my_syscall6

    Required by future forced pselect6/pselect6_time64, tested on arm/vexpress-a9

    (Review suggestions from Arnd)

* tools/nolibc: open: fix up compile warning for arm

    A trivial fixup based on compiler's suggestion and glibc code

Best regards,
Zhangjin

----
[1]: https://lore.kernel.org/linux-riscv/20230529113143.GB2762@1wt.eu/T/#t

Zhangjin Wu (7):
  selftests/nolibc: syscall_args: use __NR_statx for rv32
  selftests/nolibc: allow specify extra arguments for qemu
  selftests/nolibc: fix up compile warning with glibc on x86_64
  selftests/nolibc: not include limits.h for nolibc
  selftests/nolibc: use INT_MAX instead of __INT_MAX__
  tools/nolibc: arm: add missing my_syscall6
  tools/nolibc: open: fix up compile warning for arm

 tools/include/nolibc/arch-arm.h              | 23 ++++++++++++++++++++
 tools/include/nolibc/stdint.h                | 14 ++++++++++++
 tools/include/nolibc/sys.h                   |  2 +-
 tools/testing/selftests/nolibc/Makefile      |  2 +-
 tools/testing/selftests/nolibc/nolibc-test.c | 14 +++++++-----
 5 files changed, 47 insertions(+), 8 deletions(-)

-- 
2.25.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2023-05-29 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 12:52 Zhangjin Wu [this message]
2023-05-29 12:54 ` [PATCH v2 1/7] selftests/nolibc: syscall_args: use generic __NR_statx Zhangjin Wu
2023-05-29 12:56 ` [PATCH v2 2/7] selftests/nolibc: allow specify extra arguments for qemu Zhangjin Wu
2023-05-29 13:00 ` [PATCH v2 3/7] selftests/nolibc: fix up compile warning with glibc on x86_64 Zhangjin Wu
2023-05-29 13:04   ` Willy Tarreau
2023-05-29 13:15     ` Zhangjin Wu
2023-05-29 13:02 ` [PATCH v2 4/7] selftests/nolibc: not include limits.h for nolibc Zhangjin Wu
2023-05-29 13:04 ` [PATCH v2 5/7] selftests/nolibc: use INT_MAX instead of __INT_MAX__ Zhangjin Wu
2023-05-29 13:07 ` [PATCH v2 6/7] tools/nolibc: arm: add missing my_syscall6 Zhangjin Wu
2023-05-29 13:09 ` [PATCH v2 7/7] tools/nolibc: open: fix up compile warning for arm 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.1685362482.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=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).