public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Daniel Palmer <daniel@thingy.jp>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] tools/nolibc: large file support
Date: Sun, 19 Apr 2026 17:31:45 +0200	[thread overview]
Message-ID: <aeT1YZUQsTce6M9m@1wt.eu> (raw)
In-Reply-To: <20260418-nolibc-largefile-v1-0-b91f0775bac3@weissschuh.net>

Hi Thomas,

On Sat, Apr 18, 2026 at 12:19:55PM +0200, Thomas Weißschuh wrote:
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Thomas Weißschuh (7):
>       tools/nolibc: also handle _llseek system call
>       tools/nolibc: add __nolibc_arg_to_reg()
>       tools/nolibc: cast pointers returned from system calls through integers
>       tools/nolibc: handle 64-bit system call arguments on x32
>       tools/nolibc: handle 64-bit system call arguments on MIPS N32
>       tools/nolibc: open files with O_LARGEFILE
>       selftests/nolibc: test large file support
> 
>  tools/include/nolibc/arch-mips.h             | 94 +++++++++++++++-------------
>  tools/include/nolibc/arch-x86.h              | 70 ++++++++++-----------
>  tools/include/nolibc/crt.h                   |  4 ++
>  tools/include/nolibc/fcntl.h                 |  4 ++
>  tools/include/nolibc/sys.h                   | 14 +++--
>  tools/include/nolibc/sys/mman.h              |  6 +-
>  tools/testing/selftests/nolibc/nolibc-test.c | 48 ++++++++++++++
>  7 files changed, 153 insertions(+), 87 deletions(-)
> ---
> base-commit: 881f42cc68a6723f1fd6bac00b84b9281cf9bca0
> change-id: 20260417-nolibc-largefile-90c85e8443cf

Really great series, that's an overall ack from me:

Acked-by: Willy Tarreau <w@1wt.eu>

Please recheck the llseek commit message though.

Thanks!
Willy

      parent reply	other threads:[~2026-04-19 15:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18 10:19 [PATCH 0/7] tools/nolibc: large file support Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 1/7] tools/nolibc: also handle _llseek system call Thomas Weißschuh
2026-04-18 11:23   ` David Laight
2026-04-18 11:56     ` Thomas Weißschuh
2026-04-18 16:03       ` David Laight
2026-04-19 15:22         ` Willy Tarreau
2026-04-19 15:38           ` Thomas Weißschuh
2026-04-19 16:10             ` Willy Tarreau
2026-04-18 10:19 ` [PATCH 2/7] tools/nolibc: add __nolibc_arg_to_reg() Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 3/7] tools/nolibc: cast pointers returned from system calls through integers Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 4/7] tools/nolibc: handle 64-bit system call arguments on x32 Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 5/7] tools/nolibc: handle 64-bit system call arguments on MIPS N32 Thomas Weißschuh
2026-04-18 11:14   ` David Laight
2026-04-18 11:54     ` Thomas Weißschuh
2026-04-18 16:32       ` David Laight
2026-04-19 15:30       ` Willy Tarreau
2026-04-19 21:35         ` David Laight
2026-04-20 15:58           ` Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 6/7] tools/nolibc: open files with O_LARGEFILE Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 7/7] selftests/nolibc: test large file support Thomas Weißschuh
2026-04-18 14:01 ` [PATCH 0/7] tools/nolibc: " Daniel Palmer
2026-04-19 15:31 ` Willy Tarreau [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=aeT1YZUQsTce6M9m@1wt.eu \
    --to=w@1wt.eu \
    --cc=daniel@thingy.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    /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