From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Andreas Hindborg <a.hindborg@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Tamir Duberstein <tamird@gmail.com>
Subject: Re: linux-next: manual merge of the rust tree with the modules tree
Date: Fri, 5 Dec 2025 13:31:40 +1100 [thread overview]
Message-ID: <20251205133140.6e28f633@canb.auug.org.au> (raw)
In-Reply-To: <20251104105516.40fea116@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
Hi all,
On Tue, 4 Nov 2025 10:55:16 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the rust tree got a conflict in:
>
> rust/kernel/str.rs
>
> between commit:
>
> 51d9ee90ea90 ("rust: str: add radix prefixed integer parsing functions")
>
> from the modules tree and commit:
>
> 3b83f5d5e78a ("rust: replace `CStr` with `core::ffi::CStr`")
>
> 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/kernel/str.rs
> index a1a3581eb546,7593d758fbb7..000000000000
> --- a/rust/kernel/str.rs
> +++ b/rust/kernel/str.rs
> @@@ -10,11 -10,11 +10,13 @@@ use crate::
> };
> use core::{
> marker::PhantomData,
> - ops::{self, Deref, DerefMut, Index},
> + ops::{Deref, DerefMut, Index},
> };
>
> + pub use crate::prelude::CStr;
> +
> +pub mod parse_int;
> +
> /// Byte string without UTF-8 validity guarantee.
> #[repr(transparent)]
> pub struct BStr([u8]);
This is now a conflict between the modules 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-12-05 2:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 23:55 linux-next: manual merge of the rust tree with the modules tree Stephen Rothwell
2025-11-03 23:59 ` Miguel Ojeda
2025-11-04 8:52 ` Daniel Gomez
2025-12-05 2:31 ` 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=20251205133140.6e28f633@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=a.hindborg@kernel.org \
--cc=da.gomez@kernel.org \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=tamird@gmail.com \
/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