[klibc] [klibc:time64] resource: Avoid using <linux/resource.h>
Ben Hutchings
ben at decadent.org.uk
Sun Jan 15 11:52:51 PST 2023
On Sat, 2023-01-14 at 23:29 +0100, Arnd Bergmann wrote:
> On Sat, Jan 14, 2023, at 23:03, klibc-bot for Ben Hutchings wrote:
> > Commit-ID: d4ab7343978bbec7141f8462236ba6a47574205f
> > Gitweb:
> > http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d4ab7343978bbec7141f8462236ba6a47574205f
> > Author: Ben Hutchings <ben at decadent.org.uk>
> > AuthorDate: Sat, 14 Jan 2023 03:15:20 +0100
> > Committer: Ben Hutchings <ben at decadent.org.uk>
> > CommitDate: Sat, 14 Jan 2023 18:09:28 +0100
> >
> > [klibc] resource: Avoid using <linux/resource.h>
> >
> > Our <sys/resource.h> includes <linux/resource.h>, which includes
> > <linux/time.h>, which conflicts with 64-bit time definitions.
> >
> > Copy the definitions we actually need instead of including
> > <linux/resource.h>.
> >
> > Signed-off-by: Ben Hutchings <ben at decadent.org.uk>
>
> I had no idea we still had those definitions in linux/time.h,
> I wonder if those should be removed in the kernel, as you point
> out here there is no way this can actually work.
>
> What are the rules for klibc including kernel headers here,
> is it able to rely on the latest header version, or does
> it it have to work with old headers?
We don't make any effort to support older kernel versions, so I think
it's fine to rely on the latest kernel headers.
Ben.
--
Ben Hutchings
One of the nice things about standards is that
there are so many of them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zytor.com/archives/klibc/attachments/20230115/8fe255a4/attachment.sig>
More information about the klibc
mailing list