<?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 timerfd.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/timerfd.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/timerfd.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/timerfd.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/timerfd.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>f3ed932644a671038b31f7f536a066eeef6803b0 - selftests/nolibc: add static assertions around time types handling</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/timerfd.h#f3ed932644a671038b31f7f536a066eeef6803b0</link>
        <description>selftests/nolibc: add static assertions around time types handlingThe nolibc system call wrappers expect the libc types to be compatibleto the kernel types.Make sure these expectations hold at compile-time.Signed-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-14-c662992f75d7@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/timerfd.h</description>
        <pubDate>Sat, 20 Dec 2025 14:55:58 +0100</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
<item>
        <title>6c9be90527207f9beca78e698dd45969813f4c0e - tools/nolibc: remove time conversions</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/timerfd.h#6c9be90527207f9beca78e698dd45969813f4c0e</link>
        <description>tools/nolibc: remove time conversionsNow that &apos;struct timespec&apos; and &apos;struct __kernel_timespec&apos; arecompatible, the conversions are not necessary anymore.The same holds true for &apos;struct itimerspec&apos; and &apos;struct__kernel_itimerspec&apos;.Remove the conversions.Signed-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-11-c662992f75d7@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/timerfd.h</description>
        <pubDate>Sat, 20 Dec 2025 14:55:55 +0100</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
<item>
        <title>ba7fd0384530e3dd20ea873aac21c473e3e461ae - tools/nolibc: prefer explicit 64-bit time-related system calls</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/timerfd.h#ba7fd0384530e3dd20ea873aac21c473e3e461ae</link>
        <description>tools/nolibc: prefer explicit 64-bit time-related system callsMake sure to always use the 64-bit safe system callsin preparation for 64-bit time_t on 32-bit architectures.Also prevent issues on kernels which disable CONFIG_COMPAT_32BIT_TIMEand therefore don&apos;t provide the 32-bit system calls anymore.Signed-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-5-c662992f75d7@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/timerfd.h</description>
        <pubDate>Sat, 20 Dec 2025 14:55:49 +0100</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
<item>
        <title>e6366101ce1fab9e42ae66ff0fed5360fce65bb5 - tools/nolibc: remove __nolibc_enosys() fallback from time64-related functions</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/timerfd.h#e6366101ce1fab9e42ae66ff0fed5360fce65bb5</link>
        <description>tools/nolibc: remove __nolibc_enosys() fallback from time64-related functionsThese fallbacks where added when no explicit fallbacks for time64 wasimplemented. Now that these fallbacks are in place, the additionalfallback to __nolibc_enosys() is superfluous.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/20250821-nolibc-enosys-v1-1-4b63f2caaa89@weissschuh.net

            List of files:
            /linux/tools/include/nolibc/sys/timerfd.h</description>
        <pubDate>Thu, 21 Aug 2025 17:40:32 +0200</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;</dc:creator>
    </item>
<item>
        <title>da69cfb17b2afbb8692b74eefb844f85febb6674 - tools/nolibc: add timerfd functionality</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/include/nolibc/sys/timerfd.h#da69cfb17b2afbb8692b74eefb844f85febb6674</link>
        <description>tools/nolibc: add timerfd functionalityThis is used in various selftests and will be handy when integratingthose with nolibc.Signed-off-by: Thomas Wei&#223;schuh &lt;thomas.weissschuh@linutronix.de&gt;Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;Link: https://lore.kernel.org/r/20250428-nolibc-misc-v2-10-3c043eeab06c@linutronix.deSigned-off-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;

            List of files:
            /linux/tools/include/nolibc/sys/timerfd.h</description>
        <pubDate>Mon, 28 Apr 2025 14:40:11 +0200</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;thomas.weissschuh@linutronix.de&gt;</dc:creator>
    </item>
</channel>
</rss>
