From: Xiao Yang <ice_yangxiao@163.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Will Deacon <will@kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: Question about "asm/rwonce.h: No such file or directory"
Date: Wed, 13 Nov 2019 15:16:37 +0800 [thread overview]
Message-ID: <ac4577d4-c0f2-9596-df6f-3fcc563bde3e@163.com> (raw)
In-Reply-To: <CAK7LNARKh3-cAqsYgcxFwq9CGk-CgBfkiQgfNSULkxwO0xa2vw@mail.gmail.com>
On 11/13/19 2:57 PM, Masahiro Yamada wrote:
> Sorry, I really do not understand what you are doing.
>
> include/linux/compiler.h is only for kernel-space.
> Shrug if a user-land program includes it.
Hi Masahiro,
For building tools/bpf, it is good to fix the compiler error by Daniel's
patch(i.e. use linux/filter from linux header).
linux/compiler.h may be used by other code in kernel. Is it possible to
trigger the same error when the other code
including linux/compiler.h is built? Is this kind of code able to find
the location of <asm/rwonce.h>?
Best Regards,
Xiao Yang
next prev parent reply other threads:[~2019-11-13 7:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 8:56 Question about "asm/rwonce.h: No such file or directory" Xiao Yang
2019-11-12 12:31 ` Will Deacon
2019-11-12 12:31 ` Will Deacon
2019-11-12 12:50 ` Masahiro Yamada
2019-11-12 12:50 ` Masahiro Yamada
2019-11-12 15:13 ` Daniel Borkmann
2019-11-12 15:13 ` Daniel Borkmann
2019-11-13 3:44 ` Xiao Yang
2019-11-13 3:44 ` Xiao Yang
2019-11-13 5:28 ` Masahiro Yamada
2019-11-13 5:28 ` Masahiro Yamada
2019-11-13 5:51 ` Xiao Yang
2019-11-13 5:51 ` Xiao Yang
2019-11-13 6:57 ` Masahiro Yamada
2019-11-13 6:57 ` Masahiro Yamada
2019-11-13 7:16 ` Xiao Yang [this message]
2019-11-13 7:16 ` Xiao Yang
2019-11-13 7:53 ` Masahiro Yamada
2019-11-13 7:53 ` Masahiro Yamada
2019-11-13 8:35 ` Xiao Yang
2019-11-13 8:35 ` Xiao Yang
2019-11-13 8:54 ` Masahiro Yamada
2019-11-13 8:54 ` Masahiro Yamada
2019-11-13 14:55 ` Xiao Yang
2019-11-13 14:55 ` Xiao Yang
2019-11-13 15:48 ` Masahiro Yamada
2019-11-13 15:48 ` Masahiro Yamada
2019-11-13 0:59 ` Xiao Yang
2019-11-13 0:59 ` Xiao Yang
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=ac4577d4-c0f2-9596-df6f-3fcc563bde3e@163.com \
--to=ice_yangxiao@163.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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