From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] kbuild: fix scripts/headers.sh to see the correct Kbuild path
Date: Tue, 13 Jan 2015 14:24:04 +0900 [thread overview]
Message-ID: <20150113142404.CACA.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <1417589535-15867-1-git-send-email-yamada.m@jp.panasonic.com>
Hi Sam,
IIRC, you mentioned scripts/headers.sh is pointless
and should be removed from the code base.
If so, this patch of mine has no point.
Could you consider removing scripts/headers.sh ?
Best Regards
Masahiro Yamada
On Wed, 3 Dec 2014 15:52:15 +0900
Masahiro Yamada <yamada.m@jp.panasonic.com> 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>
> ---
>
> scripts/headers.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/headers.sh b/scripts/headers.sh
> index 95ece06..b164336 100755
> --- a/scripts/headers.sh
> +++ b/scripts/headers.sh
> @@ -6,7 +6,7 @@ set -e
>
> do_command()
> {
> - if [ -f ${srctree}/arch/$2/include/asm/Kbuild ]; then
> + if [ -f ${srctree}/arch/$2/include/uapi/asm/Kbuild ]; then
> make ARCH=$2 KBUILD_HEADERS=$1 headers_$1
> else
> printf "Ignoring arch: %s\n" ${arch}
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-13 5:24 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
2015-01-13 5:24 ` Masahiro Yamada [this message]
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=20150113142404.CACA.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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