public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the arm64 tree with the kbuild tree
Date: Thu, 25 Sep 2025 13:39:49 -0400	[thread overview]
Message-ID: <20250925173949.GA489036@ax162> (raw)
In-Reply-To: <aNU-sG84vqPj7p7G@sirena.org.uk>

On Thu, Sep 25, 2025 at 02:08:00PM +0100, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the arm64 tree got a conflict in:
> 
>   arch/arm64/Kconfig
> 
> between commit:
> 
>   23cb0514208da ("arm64: Remove tautological LLVM Kconfig conditions")
> 
> from the kbuild tree and commit:
> 
>   1cf89b6bf660c ("arm64: Kconfig: Make CPU_BIG_ENDIAN depend on BROKEN")
> 
> from the arm64 tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> diff --cc arch/arm64/Kconfig
> index 56eec3586ff77,69bde40e19e23..0000000000000
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@@ -1492,6 -1494,8 +1494,7 @@@ choic
>   
>   config CPU_BIG_ENDIAN
>   	bool "Build big-endian kernel"
>  -	# https://github.com/llvm/llvm-project/commit/1379b150991f70a5782e9a143c2ba5308da1161c
>  -	depends on (AS_IS_GNU || AS_VERSION >= 150000) && BROKEN
> ++	depends on BROKEN
>   	help
>   	  Say Y if you plan on running a kernel with a big-endian userspace.
>   

Thanks for the heads up, this looks correct to me.

Cheers,
Nathan

      reply	other threads:[~2025-09-25 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 13:08 linux-next: manual merge of the arm64 tree with the kbuild tree Mark Brown
2025-09-25 17:39 ` Nathan Chancellor [this message]

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=20250925173949.GA489036@ax162 \
    --to=nathan@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox