All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>, Matt Hart <matthew.hart@linaro.org>
Cc: Tri Vo <trong@google.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nathan Huckleberry <nhuck@google.com>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Nathan Chancellor <natechancellor@gmail.com>,
	Will Deacon <will@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: Disable big endian builds with clang
Date: Wed, 7 Aug 2019 17:01:45 +0100	[thread overview]
Message-ID: <20190807160145.GG4048@sirena.co.uk> (raw)
In-Reply-To: <ec7bef46-7dcf-d165-b772-b4fd6055d964@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]

On Wed, Aug 07, 2019 at 03:41:25PM +0100, Robin Murphy wrote:
> On 07/08/2019 13:38, Mark Brown wrote:

> > 	https://storage.kernelci.org/next/master/next-20190730/arm64/defconfig+CONFIG_CPU_BIG_ENDIAN=y/clang-8/lab-baylibre/boot-meson-gxbb-nanopi-k2.html

> I thought it looked suspicious that there were EFI messages in that boot
> log; from that job's config: https://storage.kernelci.org/next/master/next-20190730/arm64/defconfig+CONFIG_CPU_BIG_ENDIAN=y/clang-8/kernel.config

> ...
> # CONFIG_CPU_BIG_ENDIAN is not set
> ...

> I think that's a kernelci problem...

Ugh, right.  It's possible there's some issue in Kconfig which is
causing the steps we take to add in the extra config options to break
when clang is used but I'd be a little surprised.  Copying in Matt here
as well, I've filed a ticket in the KernelCI issue tracker:

	https://github.com/kernelci/kernelci-core/issues/136

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-08-07 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 18:39 [PATCH] arm64: Disable big endian builds with clang Mark Brown
2019-08-06 21:25 ` Nick Desaulniers
2019-08-06 23:47   ` Nick Desaulniers
2019-08-07 12:38     ` Mark Brown
2019-08-07 14:41       ` Robin Murphy
2019-08-07 16:01         ` Mark Brown [this message]
2019-08-07 13:01 ` Mark Rutland
2019-08-07 13:05   ` Mark Brown
2019-08-07 13:56     ` Mark Rutland
2019-08-07 14:14       ` Mark Rutland
2019-08-07 15:29       ` Mark Brown
2019-08-07 15:43         ` Mark Rutland
2019-08-07 16:19           ` Mark Brown

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=20190807160145.GG4048@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=matthew.hart@linaro.org \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=nhuck@google.com \
    --cc=robin.murphy@arm.com \
    --cc=trong@google.com \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.