From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: johannes.berg@intel.com, ndesaulniers@google.com,
pihsun@chromium.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless: Use linux/stddef.h instead of stddef.h
Date: Mon, 25 May 2020 11:35:46 +0200 [thread overview]
Message-ID: <2555103.LUZAIfNjjX@pc-42> (raw)
In-Reply-To: <20200521201422.16493-1-hauke@hauke-m.de>
On Thursday 21 May 2020 22:14:22 CEST Hauke Mehrtens wrote:
> When compiling inside the kernel include linux/stddef.h instead of
> stddef.h. When I compile this header file in backports for power PC I
> run into a conflict with ptrdiff_t. I was unable to reproduce this in
> mainline kernel. I still would like to fix this problem in the kernel.
>
> Fixes: 6989310f5d43 ("wireless: Use offsetof instead of custom macro.")
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> include/uapi/linux/wireless.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/wireless.h b/include/uapi/linux/wireless.h
> index a2c006a364e0..24f3371ad826 100644
> --- a/include/uapi/linux/wireless.h
> +++ b/include/uapi/linux/wireless.h
> @@ -74,7 +74,11 @@
> #include <linux/socket.h> /* for "struct sockaddr" et al */
> #include <linux/if.h> /* for IFNAMSIZ and co... */
>
> -#include <stddef.h> /* for offsetof */
> +#ifdef __KERNEL__
> +# include <linux/stddef.h> /* for offsetof */
> +#else
> +# include <stddef.h> /* for offsetof */
> +#endif
Hello,
This patch also solves a warning I encountered when I launched sparse
(with make C=1):
/usr/lib/gcc-cross/arm-linux-gnueabihf/9/include/stddef.h:406:9: warning: preprocessor token offsetof redefined
./include/linux/stddef.h:17:9: this was the original definition
However, I wonder if it useful to keep 'include <stddef.h>' when this file
is included from userspace. If it does not compile anymore, there is
problem somewhere else, no?
(Globally, I always find suspicious a kernel source that includes a system
header)
--
Jérôme Pouiller
next prev parent reply other threads:[~2020-05-25 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 20:14 [PATCH] wireless: Use linux/stddef.h instead of stddef.h Hauke Mehrtens
2020-05-25 9:35 ` Jérôme Pouiller [this message]
2020-05-26 21:02 ` Hauke Mehrtens
2020-05-27 14:03 ` Jérôme Pouiller
2020-06-11 14:00 ` Hauke Mehrtens
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=2555103.LUZAIfNjjX@pc-42 \
--to=jerome.pouiller@silabs.com \
--cc=hauke@hauke-m.de \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=pihsun@chromium.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).