<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in ioctl.h</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6285f0881ec68034399d13552f7243e69e6e37bf - tools/nolibc: rename sys_foo() functions to _sys_foo()</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/ioctl.h#6285f0881ec68034399d13552f7243e69e6e37bf</link>
        <description>tools/nolibc: rename sys_foo() functions to _sys_foo()The sys_foo() naming scheme used by the syscall wrappers may collidewith application symbols. Especially as &apos;sys_&apos; is an obvious namingscheme an application may choose for its own custom systemcall wrappers.Avoid these conflicts by using an leading underscore which moves thenames into the implementation&apos;s namespace. This naming scheme was chosenover a &apos;__nolibc_&apos; prefix, as these functions are not an implementationdetail but a documented interface meant to be used by applications.While this may break some existing users, adapting them should bestraightforward. Given that nolibc is most-likely vendored, nounexpected breakage should happen. No in-tree users are affected.These conflicts happen when compiling some of the kernel selftestswith nolibc.Signed-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Link: https://patch.msgid.link/20260319-nolibc-namespacing-v1-1-33c22eaddb5e@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/ioctl.h</description>
        <pubDate>Thu, 19 Mar 2026 17:20:17 +0100</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
<item>
        <title>55f1d6a9d6780e779e882a4d2d1b3db311835798 - tools/nolibc: rename my_syscallX() to __nolibc_syscallX()</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/ioctl.h#55f1d6a9d6780e779e882a4d2d1b3db311835798</link>
        <description>tools/nolibc: rename my_syscallX() to __nolibc_syscallX()The naming convention of the my_syscallX() macros is a bit unfortunate.They may conflict with application code and the name is very generic.Switch to __nolibc_syscallX(). The leading underscores place the symbolsin the implementation-defined namespace, avoiding conflicting names.It is also clearer that these are non-standard extensions from nolibc.Signed-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Link: https://patch.msgid.link/20260223-nolibc-namespacing-v1-1-52574ffebb2c@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/ioctl.h</description>
        <pubDate>Mon, 23 Feb 2026 22:40:14 +0100</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
<item>
        <title>7281be583117d7ff12c52684ffc732e6ffca8f58 - tools/nolibc: move ioctl() to sys/ioctl.h</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/ioctl.h#7281be583117d7ff12c52684ffc732e6ffca8f58</link>
        <description>tools/nolibc: move ioctl() to sys/ioctl.hThis is the location regular userspace expects this definition.Signed-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Link: https://lore.kernel.org/r/20250515-nolibc-sys-v1-1-74f82eea3b59@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/ioctl.h</description>
        <pubDate>Thu, 15 May 2025 21:57:47 +0200</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
</channel>
</rss>
