From: Richard Kuo <rkuo@codeaurora.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-hexagon@vger.kernel.org, linux-kbuild@vger.kernel.org,
Michal Marek <mmarek@suse.com>, Sam Ravnborg <sam@ravnborg.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hexagon: get rid of #include <generated/compile.h>
Date: Wed, 27 Sep 2017 18:24:15 -0500 [thread overview]
Message-ID: <20170927232415.GB5939@codeaurora.org> (raw)
In-Reply-To: <1505920670-8290-1-git-send-email-yamada.masahiro@socionext.com>
On Thu, Sep 21, 2017 at 12:17:50AM +0900, Masahiro Yamada wrote:
> <generated/compile.h> is created (or updated) when Kbuild descends
> into the init/ directory. In parallel building from a pristine
> source tree, there is no guarantee <generated/compile.h> exists when
> arch/hexagon/kernel/ptrace.c is compiled.
>
> For hexagon architecture, we know UTS_MACHINE is a fixed string
> "hexagon", so let's hard-code it, like many architectures do.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> arch/hexagon/kernel/ptrace.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
Acked-by: Richard Kuo <rkuo@codeaurora.org>
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-09-27 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 15:17 [PATCH] hexagon: get rid of #include <generated/compile.h> Masahiro Yamada
2017-09-27 23:24 ` Richard Kuo [this message]
2017-10-03 1:26 ` Masahiro Yamada
2017-10-09 14:25 ` Masahiro Yamada
2017-10-09 16:31 ` Richard Kuo
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=20170927232415.GB5939@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=oleg@redhat.com \
--cc=sam@ravnborg.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 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.