public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
	Jamie Cunliffe <Jamie.Cunliffe@arm.com>,
	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 rust tree with the arm64 tree
Date: Tue, 12 Mar 2024 09:35:54 +1100	[thread overview]
Message-ID: <20240312093554.757be026@canb.auug.org.au> (raw)
In-Reply-To: <20240301153807.796a3a28@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Hi all,

On Fri, 1 Mar 2024 15:38:07 +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:
> 
>   f82811e22b48 ("rust: Refactor the build target to allow the use of builtin targets")
> 
> from the arm64 tree and commit:
> 
>   ecab4115c44c ("kbuild: mark `rustc` (and others) invocations as recursive")
> 
> 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.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc rust/Makefile
> index fe045dbc701e,a78fcf4004b0..000000000000
> --- a/rust/Makefile
> +++ b/rust/Makefile
> @@@ -435,11 -434,8 +435,11 @@@ $(obj)/core.o: private skip_clippy = 
>   $(obj)/core.o: private skip_flags = -Dunreachable_pub
>   $(obj)/core.o: private rustc_objcopy = $(foreach sym,$(redirect-intrinsics),--redefine-sym $(sym)=__rust$(sym))
>   $(obj)/core.o: private rustc_target_flags = $(core-cfgs)
>  -$(obj)/core.o: $(RUST_LIB_SRC)/core/src/lib.rs scripts/target.json FORCE
>  +$(obj)/core.o: $(RUST_LIB_SRC)/core/src/lib.rs FORCE
> - 	$(call if_changed_dep,rustc_library)
> + 	+$(call if_changed_dep,rustc_library)
>  +ifneq ($(or $(CONFIG_X86_64),$(CONFIG_LOONGARCH)),)
>  +$(obj)/core.o: scripts/target.json
>  +endif
>   
>   $(obj)/compiler_builtins.o: private rustc_objcopy = -w -W '__*'
>   $(obj)/compiler_builtins.o: $(src)/compiler_builtins.rs $(obj)/core.o FORCE

This is now a conflict between the arm64 tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2024-03-11 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01  4:38 linux-next: manual merge of the rust tree with the arm64 tree Stephen Rothwell
2024-03-01  9:42 ` Miguel Ojeda
2024-03-11 22:35 ` 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=20240312093554.757be026@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Jamie.Cunliffe@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ojeda@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