From: Mark Brown <broonie@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h
Date: Wed, 21 May 2025 14:22:30 +0100 [thread overview]
Message-ID: <744a1aa8-1efc-4c20-b45e-070fc038f6e8@sirena.org.uk> (raw)
In-Reply-To: <89bb5a3e-dd6c-475d-9c5d-0bd1595be735@t-8ch.de>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Wed, May 21, 2025 at 03:08:05PM +0200, Thomas Weißschuh wrote:
> On 2025-05-21 14:03:37+0100, Mark Brown wrote:
> > > +/* make sure to include all global symbols */
> > > +#include "nolibc.h"
> > assumes that the nolibc include directory is in the include path, or
> > otherwise set up with a -I path, previously you just had to include
> > nolibc.h with the includes that are there working due to being relative
> > to nolibc.h. I'll send a patch for the arm64 tests.
> Thanks for the report.
> Inside sys/ this should actually be #include "../nolibc.h".
> I'll doublecheck all of sys/ and see why our new header checks didn't
> catch this.
Ah, you expect what's currently there to work - good. I noticed that
the vDSO tests had a -I for the nolibc directory which made me think it
was expected that it be there, it's the only user on most arches.
> > It looks like the RISC-V selftests are also impacted, I didn't spot any
> > other users that didn't already have an -I.
> No changes to the selftests should be necessary.
OK, that's easier for me!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-21 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 19:57 [PATCH 0/9] tools/nolibc: split out more headers Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h Thomas Weißschuh
2025-05-21 13:03 ` Mark Brown
2025-05-21 13:08 ` Thomas Weißschuh
2025-05-21 13:22 ` Mark Brown [this message]
2025-05-21 13:45 ` Thomas Weißschuh
2025-05-21 13:58 ` Mark Brown
2025-05-21 18:49 ` Mark Brown
2025-05-23 8:33 ` Thomas Weißschuh
2025-05-23 10:14 ` Mark Brown
2025-05-15 19:57 ` [PATCH 2/9] tools/nolibc: move mount() to sys/mount.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 3/9] tools/nolibc: move prctl() to sys/prctl.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 4/9] tools/nolibc: move reboot() to sys/reboot.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 5/9] tools/nolibc: move getrlimit() and friends to sys/resource.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 6/9] tools/nolibc: move makedev() and friends to sys/sysmacros.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 7/9] tools/nolibc: move uname() and friends to sys/utsname.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 8/9] tools/nolibc: move NULL and offsetof() to sys/stddef.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 9/9] selftests/nolibc: drop include guards around standard headers Thomas Weißschuh
2025-05-16 3:50 ` [PATCH 0/9] tools/nolibc: split out more headers 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=744a1aa8-1efc-4c20-b45e-070fc038f6e8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--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).