From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] tools/nolibc: make dev_t 64 bits wide
Date: Sat, 4 Apr 2026 10:26:09 +0200 [thread overview]
Message-ID: <adDLIayt4Hx_b8Ix@1wt.eu> (raw)
In-Reply-To: <20260404-nolibc-makedev-v2-0-456a429bf60c@weissschuh.net>
Hi Thomas,
On Sat, Apr 04, 2026 at 10:08:17AM +0200, Thomas Weißschuh wrote:
> Handle all possible values of minor and major numbers.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Changes in v2:
> - Stay compatible with applications expecting makedev(), major() or
> minor() to be macros.
> - Link to v1: https://patch.msgid.link/20260331-nolibc-makedev-v1-0-ee79ee31e4d6@weissschuh.net
Thanks for this. Your series looks good to me. I was also initially
concerned by the loss of macros but you addressed it in this series
so everything's fine from my perspective.
Acked-by: Willy Tarreau <w@1wt.eu>
Thanks,
willy
prev parent reply other threads:[~2026-04-04 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 8:08 Thomas Weißschuh
2026-04-04 8:08 ` [PATCH v2 1/6] selftests/nolibc: add some tests for makedev() and friends Thomas Weißschuh
2026-04-04 8:08 ` [PATCH v2 2/6] selftests/nolibc: add a test for stat().st_rdev Thomas Weißschuh
2026-04-04 8:08 ` [PATCH v2 3/6] tools/nolibc: move the logic of makedev() and friends into functions Thomas Weißschuh
2026-04-04 8:08 ` [PATCH v2 4/6] tools/nolibc: make dev_t 64 bits wide Thomas Weißschuh
2026-04-04 8:08 ` [PATCH v2 5/6] tools/nolibc: handle all major and minor numbers in makedev() and friends Thomas Weißschuh
2026-04-04 8:08 ` [PATCH v2 6/6] tools/nolibc: use makedev() in fstatat() Thomas Weißschuh
2026-04-04 8:26 ` 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=adDLIayt4Hx_b8Ix@1wt.eu \
--to=w@1wt.eu \
--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
all inboxes | Powered by JetHome®