From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: linux-hexagon@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <mmarek@suse.com>, Sam Ravnborg <sam@ravnborg.org>,
Oleg Nesterov <oleg@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hexagon: get rid of #include <generated/compile.h>
Date: Mon, 9 Oct 2017 23:25:28 +0900 [thread overview]
Message-ID: <CAK7LNARd6ovx=qmny1micPx7BUXf9uL9soES_OcotF-bYCCQWw@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQaGd5h5OHe5ArXV=wms07Zpd4OBPLrPYwZ68KpbjeGcQ@mail.gmail.com>
2017-10-03 10:26 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> Hi Richard,
>
> 2017-09-28 8:24 GMT+09:00 Richard Kuo <rkuo@codeaurora.org>:
>> 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>
>>
>
> How should this patch be handled?
>
I checked
git://git.kernel.org/pub/scm/linux/kernel/git/rkuo/linux-hexagon-kernel.git
I could not see any patch applied to the tree since last year.
Assuming the tree is unmaintained, I am picking this patch to Kbuild tree.
Applied to linux-kbuild/kbuild with Rechard's Acked.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2017-10-09 14:26 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
2017-10-03 1:26 ` Masahiro Yamada
2017-10-09 14:25 ` Masahiro Yamada [this message]
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='CAK7LNARd6ovx=qmny1micPx7BUXf9uL9soES_OcotF-bYCCQWw@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--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=rkuo@codeaurora.org \
--cc=sam@ravnborg.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).