linux-kernel - Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <25a18e14-8ac9-4ac8-8907-a087050b1eb6@t-8ch.de>
Date: Fri, 23 May 2025 10:33:13 +0200
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Mark Brown <broonie@...nel.org>
Cc: Willy Tarreau <w@....eu>, Shuah Khan <shuah@...nel.org>, 
	linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h

On 2025-05-21 19:49:39+0100, Mark Brown wrote:
> On Wed, May 21, 2025 at 03:45:42PM +0200, Thomas Weißschuh wrote:
> 
> > Or you could run your testsuite with the new nolibc for-next branch
> > which should be fixed now.
> 
> That seems to build with 869c788909b93a78ead1ca28c42b95eeb0779215 which
> is the current HEAD of:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git for-next

Thanks for testing!

To be sure, was this your full test-run? Or did you do a full test-run
on linux-next in the meantime?
I'd like to get your confirmation before sending these changes to Linus.


Thomas