mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Mark Brown" <broonie@kernel.org>, "Miguel Ojeda" <ojeda@kernel.org>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
	"Gary Guo" <gary@garyguo.net>,
	"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 origin tree
Date: Mon, 30 Mar 2026 14:26:15 +0100	[thread overview]
Message-ID: <DHG5G61H8WGB.1UL0YPOVFUWFO@garyguo.net> (raw)
In-Reply-To: <acp4AY8W5_jOo56Z@sirena.org.uk>

On Mon Mar 30, 2026 at 2:17 PM BST, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the rust tree got a conflict in:
>
>   scripts/Makefile.build
>
> between commit:
>
>   f41941aab3acd ("rust: ptr: add projection infrastructure")

This commit is in v7.0-rc4 and later. Miguel, perhaps do a back merge to resolve
the conflict?

>
> from the origin tree and commit:
>
>   560a7a9b9267f ("rust: add `const_assert!` macro")
>
> 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 scripts/Makefile.build
> index 3652b85be5459,a6d1a2b210aaa..0000000000000
> --- a/scripts/Makefile.build
> +++ b/scripts/Makefile.build
> @@@ -310,7 -310,7 +310,8 @@@ $(obj)/%.lst: $(obj)/%.c FORC
>   
>   # The features in this list are the ones allowed for non-`rust/` code.
>   #
>  +#   - Stable since Rust 1.79.0: `feature(slice_ptr_len)`.
> + #   - Stable since Rust 1.79.0: `feature(inline_const)`.

I think we would want the lines to be merged on rust-next. This is fine on
linux-next, though.

>   #   - Stable since Rust 1.81.0: `feature(lint_reasons)`.
>   #   - Stable since Rust 1.82.0: `feature(asm_const)`,
>   #     `feature(offset_of_nested)`, `feature(raw_ref_op)`.
> @@@ -321,7 -320,7 +322,7 @@@
>   #
>   # Please see https://github.com/Rust-for-Linux/linux/issues/2 for details on
>   # the unstable features in use.
> - rust_allowed_features := asm_const,asm_goto,arbitrary_self_types,lint_reasons,offset_of_nested,raw_ref_op,slice_ptr_len,strict_provenance,used_with_arg
>  -rust_allowed_features := asm_const,asm_goto,arbitrary_self_types,inline_const,lint_reasons,offset_of_nested,raw_ref_op,used_with_arg
> ++rust_allowed_features := asm_const,asm_goto,arbitrary_self_types,inline_const,lint_reasons,offset_of_nested,raw_ref_op,slice_ptr_lenstrict_provenance,used_with_arg

I think this is missing a comma between slice_ptr_len and strict_provenance.

>   
>   # `--out-dir` is required to avoid temporaries being created by `rustc` in the
>   # current working directory, which may be not accessible in the out-of-tree

Thanks,
Gary


  reply	other threads:[~2026-03-30 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 13:17 Mark Brown
2026-03-30 13:26 ` Gary Guo [this message]
2026-03-30 13:30   ` Miguel Ojeda
2026-03-30 13:32     ` Miguel Ojeda
  -- strict thread matches above, loose matches on Subject: below --
2026-04-06 13:13 Mark Brown
2026-04-06 13:16 ` Miguel Ojeda
2026-04-06 13:12 Mark Brown
2026-04-06 13:15 ` Miguel Ojeda
2026-04-06 13:02 Mark Brown
2026-04-06 13:11 ` Miguel Ojeda
2026-04-06 13:14   ` Mark Brown
2026-04-03 12:35 Mark Brown
2026-04-03 12:53 ` Miguel Ojeda
2021-12-13 22:33 broonie

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=DHG5G61H8WGB.1UL0YPOVFUWFO@garyguo.net \
    --to=gary@garyguo.net \
    --cc=broonie@kernel.org \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ojeda@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

all inboxes | Powered by JetHome®