From: Michal Marek <mmarek@suse.cz>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] kbuild: create symbolic link only for ARM, SPARC, PowerPC, x86
Date: Tue, 26 May 2015 15:14:03 +0800 [thread overview]
Message-ID: <55641D3B.7070300@suse.cz> (raw)
In-Reply-To: <1432621975-4582-3-git-send-email-yamada.masahiro@socionext.com>
Dne 26.5.2015 v 14:32 Masahiro Yamada napsal(a):
> The symbolic link to SoC/CPU specific header directory is created
> during the build, while it is only necessary for ARM, SPARC, x86,
> and some CPUs of PowerPC. For the other architectures, it just
> results in a broken symbolic link.
>
> Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
> links.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> arch/Kconfig | 6 ++++++
> arch/powerpc/Kconfig | 3 +++
> scripts/Makefile.autoconf | 2 ++
> 3 files changed, 11 insertions(+)
[...]
> diff --git a/scripts/Makefile.autoconf b/scripts/Makefile.autoconf
> index f054081..a17e374 100644
> --- a/scripts/Makefile.autoconf
> +++ b/scripts/Makefile.autoconf
> @@ -106,6 +106,7 @@ include/config.h: scripts/Makefile.autoconf create_symlink FORCE
> # Otherwise, create a symbolic link to arch/$(ARCH)/include/asm/arch-$(SOC).
> PHONY += create_symlink
> create_symlink:
> +ifeq ($(CONFIG_CREATE_ARCH_SYMLINK),y)
'ifdef CONFIG_CREATE_ARCH_SYMLINK' is shorter and maybe easier to read.
But you confused me, I thought this was a kernel patch at first :).
Michal
next prev parent reply other threads:[~2015-05-26 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 6:32 [U-Boot] [PATCH 0/2] Masahiro Yamada
2015-05-26 6:32 ` [U-Boot] [PATCH 1/2] nds32: include <asm/arch-*/*.h> instead of <asm/arch/*.h> Masahiro Yamada
2015-05-26 6:32 ` [U-Boot] [PATCH 2/2] kbuild: create symbolic link only for ARM, SPARC, PowerPC, x86 Masahiro Yamada
2015-05-26 7:14 ` Michal Marek [this message]
2015-05-26 9:14 ` Masahiro Yamada
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=55641D3B.7070300@suse.cz \
--to=mmarek@suse.cz \
--cc=u-boot@lists.denx.de \
/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