public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Masahiro Yamada <masahiroy@kernel.org>, linux-kbuild@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	linux-parisc@vger.kernel.org, linux-xtensa@linux-xtensa.org
Subject: Re: [PATCH 2/2] arch: use cross_compiling to check whether it is a cross build or not
Date: Mon, 3 May 2021 15:16:47 +0200	[thread overview]
Message-ID: <939b93cf-a116-da76-8fde-fa4fe1b42ce4@gmx.de> (raw)
In-Reply-To: <20210501172437.156926-2-masahiroy@kernel.org>

On 5/1/21 7:24 PM, Masahiro Yamada wrote:
> 'cross_compiling' is defined by the top Makefile and available for
> arch Makefiles to check whether it is a cross build or not. A good
> thing is the variable name 'cross_compiling' is self-documenting.
>
> This is a simple replacement for m68k, mips, sh, for which $(ARCH)
> and $(SRCARCH) always match.
>
> No functional change is intended for xtensa, either.
>
> This is rather a fix for parisc because arch/parisc/Makefile defines
> UTS_MATCHINE depending on CONFIG_64BIT, therefore cc-cross-prefix
> is not working in Kconfig time.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
>   arch/m68k/Makefile   | 2 +-
>   arch/mips/Makefile   | 2 +-
>   arch/parisc/Makefile | 2 +-

Acked-by: Helge Deller <deller@gmx.de>  # parisc

Thanks!
Helge

  parent reply	other threads:[~2021-05-03 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 17:24 [PATCH 1/2] kbuild: remove ARCH=sh64 support from top Makefile Masahiro Yamada
2021-05-01 17:24 ` [PATCH 2/2] arch: use cross_compiling to check whether it is a cross build or not Masahiro Yamada
2021-05-03 12:53   ` Geert Uytterhoeven
2021-05-03 13:16   ` Helge Deller [this message]
2021-05-04  9:45   ` Max Filippov
2021-05-06 12:11   ` Rob Landley
2021-05-01 21:18 ` [PATCH 1/2] kbuild: remove ARCH=sh64 support from top Makefile Arnd Bergmann
2021-05-05 17:47   ` 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=939b93cf-a116-da76-8fde-fa4fe1b42ce4@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arnd@arndb.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=masahiroy@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=ysato@users.sourceforge.jp \
    /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