From: ebiederm@xmission.com (Eric W. Biederman) To: "Dmitry V. Levin" <ldv@altlinux.org> Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] uapi: fix linux/kexec.h userspace compilation errors Date: Thu, 23 Feb 2017 14:37:46 +1300 [thread overview] Message-ID: <87h93l3cwl.fsf@xmission.com> (raw) In-Reply-To: <20170222224646.GC14311@altlinux.org> (Dmitry V. Levin's message of "Thu, 23 Feb 2017 01:46:46 +0300") "Dmitry V. Levin" <ldv@altlinux.org> writes: > Include <stddef.h> (guarded by #ifndef __KERNEL__) to fix the following > linux/kexec.h userspace compilation errors: > > /usr/include/linux/kexec.h:53:2: error: unknown type name 'size_t' > size_t bufsz; > /usr/include/linux/kexec.h:55:2: error: unknown type name 'size_t' > size_t memsz; Were these failures generated with a static checker? What changed that you are seeing new failures in old essentially static headers? Eric > Signed-off-by: Dmitry V. Levin <ldv@altlinux.org> > --- > include/uapi/linux/kexec.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/include/uapi/linux/kexec.h b/include/uapi/linux/kexec.h > index aae5ebf..7def5f5 100644 > --- a/include/uapi/linux/kexec.h > +++ b/include/uapi/linux/kexec.h > @@ -45,6 +45,9 @@ > #define KEXEC_SEGMENT_MAX 16 > > #ifndef __KERNEL__ > + > +#include <stddef.h> /* For size_t. */ > + > /* > * This structure is used to hold the arguments that are used when > * loading kernel binaries.
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman) To: "Dmitry V. Levin" <ldv@altlinux.org> Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] uapi: fix linux/kexec.h userspace compilation errors Date: Thu, 23 Feb 2017 14:37:46 +1300 [thread overview] Message-ID: <87h93l3cwl.fsf@xmission.com> (raw) In-Reply-To: <20170222224646.GC14311@altlinux.org> (Dmitry V. Levin's message of "Thu, 23 Feb 2017 01:46:46 +0300") "Dmitry V. Levin" <ldv@altlinux.org> writes: > Include <stddef.h> (guarded by #ifndef __KERNEL__) to fix the following > linux/kexec.h userspace compilation errors: > > /usr/include/linux/kexec.h:53:2: error: unknown type name 'size_t' > size_t bufsz; > /usr/include/linux/kexec.h:55:2: error: unknown type name 'size_t' > size_t memsz; Were these failures generated with a static checker? What changed that you are seeing new failures in old essentially static headers? Eric > Signed-off-by: Dmitry V. Levin <ldv@altlinux.org> > --- > include/uapi/linux/kexec.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/include/uapi/linux/kexec.h b/include/uapi/linux/kexec.h > index aae5ebf..7def5f5 100644 > --- a/include/uapi/linux/kexec.h > +++ b/include/uapi/linux/kexec.h > @@ -45,6 +45,9 @@ > #define KEXEC_SEGMENT_MAX 16 > > #ifndef __KERNEL__ > + > +#include <stddef.h> /* For size_t. */ > + > /* > * This structure is used to hold the arguments that are used when > * loading kernel binaries. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-02-23 1:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-22 22:46 [PATCH] uapi: fix linux/kexec.h userspace compilation errors Dmitry V. Levin 2017-02-22 22:46 ` Dmitry V. Levin 2017-02-23 1:37 ` Eric W. Biederman [this message] 2017-02-23 1:37 ` Eric W. Biederman 2017-02-23 2:07 ` Dmitry V. Levin 2017-02-23 2:07 ` Dmitry V. Levin
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=87h93l3cwl.fsf@xmission.com \ --to=ebiederm@xmission.com \ --cc=kexec@lists.infradead.org \ --cc=ldv@altlinux.org \ --cc=linux-kernel@vger.kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.