From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"WANG Rui" <wangrui@loongson.cn>
Subject: Re: linux-next: manual merge of the rust tree with the loongarch tree
Date: Tue, 1 Apr 2025 11:26:57 +1100 [thread overview]
Message-ID: <20250401112657.5df1001c@canb.auug.org.au> (raw)
In-Reply-To: <20250331160726.4e3d93dd@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
Hi all,
On Mon, 31 Mar 2025 16:07:26 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the rust tree got a conflict in:
>
> rust/Makefile
>
> between commit:
>
> 13c23cb4ed09 ("rust: Fix enabling Rust and building with GCC for LoongArch")
>
> from the loongarch tree and commit:
>
> 6b2dab17d6fa ("rust: pass correct target to bindgen on Usermode Linux")
>
> from the rust 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 rust/Makefile
> index 1750affda774,b9cc810764e9..000000000000
> --- a/rust/Makefile
> +++ b/rust/Makefile
> @@@ -251,8 -274,7 +279,9 @@@ bindgen_skip_c_flags := -mno-fp-ret-in-
> # Derived from `scripts/Makefile.clang`.
> BINDGEN_TARGET_x86 := x86_64-linux-gnu
> BINDGEN_TARGET_arm64 := aarch64-linux-gnu
> +BINDGEN_TARGET_arm := arm-linux-gnueabi
> +BINDGEN_TARGET_loongarch := loongarch64-linux-gnusf
> + BINDGEN_TARGET_um := $(BINDGEN_TARGET_$(SUBARCH))
> BINDGEN_TARGET := $(BINDGEN_TARGET_$(SRCARCH))
>
> # All warnings are inhibited since GCC builds are very experimental,
This is now a conflict between the loongarch tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-04-01 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 5:07 linux-next: manual merge of the rust tree with the loongarch tree Stephen Rothwell
2025-03-31 7:52 ` Miguel Ojeda
2025-04-01 0:26 ` Stephen Rothwell [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=20250401112657.5df1001c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=ojeda@kernel.org \
--cc=wangrui@loongson.cn \
/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