From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix scripts/headers.sh to see the correct Kbuild path
Date: Thu, 11 Dec 2014 10:41:19 +0900 [thread overview]
Message-ID: <20141211104119.A482.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <1418075913.2058.71.camel@x220>
Hi Paul,
On Mon, 08 Dec 2014 22:58:33 +0100
Paul Bolle <pebolle@tiscali.nl> wrote:
> Masahiro,
>
> On Wed, 2014-12-03 at 15:52 +0900, Masahiro Yamada wrote:
> > The exported headers were moved to "uapi" directories.
> > We should check the existence of arch/*/include/uapi/asm/Kbuild.
> >
> > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> > ---
>
> Does this patch fix any problems? If so, which?
I am fixing a wrong code.
Actually, the "um" architecture does not support headers install.
arch/um/include/asm/Kbuild exists
arch/um/include/uapi/asm/Kbuild does not exist
Checking arch/*/include/asm/Kbuild does not work.
Moreover, the top Makefile is checking arch/*/include/uapi/asm/Kbuild
headers_install: __headers
$(if $(wildcard $(srctree)/arch/$(hdr-arch)/include/uapi/asm/Kbuild),, \
$(error Headers not exportable for the $(SRCARCH) architecture))
> And why did no one
> notice these problems before? Perhaps the commit explanation could
> mention that.
You will notice the code below:
for arch in ${archs}; do
case ${arch} in
um) # no userspace export
;;
"um" has already been omitted and it never reaches do_command().
That is why nobody has noticed this issue.
Uh, OK, we do not need double-checking.
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-12-11 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 6:52 [PATCH] kbuild: fix scripts/headers.sh to see the correct Kbuild path Masahiro Yamada
2014-12-08 21:58 ` Paul Bolle
2014-12-11 1:41 ` Masahiro Yamada [this message]
2015-01-13 5:24 ` Masahiro Yamada
2015-01-17 21:41 ` Sam Ravnborg
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=20141211104119.A482.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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