All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>, Danilo Krummrich <dakr@kernel.org>
Cc: Gary Guo <gary@garyguo.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the drm-rust tree with the driver-core.current tree
Date: Fri, 7 Aug 2026 15:43:02 +0100	[thread overview]
Message-ID: <anXu9ocZnLLP9PYr@sirena.org.uk> (raw)

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

Hi all,

Today's linux-next merge of the drm-rust tree got a conflict in:

  rust/kernel/io.rs

between commit:

  f88db65aece9f ("rust: io: gate ioremap doctests on CONFIG_HAS_IOMEM")

from the driver-core.current tree and commits:

  65f6abf9fa816 ("rust: io: add missing safety requirement in `IoCapable` methods")
  bed01ca9e9cf8 ("rust: io: remove `MmioOwned`")

from the drm-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/kernel/io.rs
index d4063ee412000,95f46bb75f9e8..0000000000000
--- a/rust/kernel/io.rs
+++ b/rust/kernel/io.rs
@@@ -4,12 -4,20 +4,21 @@@
  //!
  //! C header: [`include/asm-generic/io.h`](srctree/include/asm-generic/io.h)
  
+ use core::{
+     marker::PhantomData,
+     mem::MaybeUninit, //
+ };
+ 
  use crate::{
      bindings,
-     prelude::*, //
+     prelude::*,
+     ptr::{
+         Alignment,
+         KnownSize, //
+     }, //
  };
  
 +#[cfg(CONFIG_HAS_IOMEM)]
  pub mod mem;
  pub mod poll;
  pub mod register;

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

             reply	other threads:[~2026-08-07 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 14:43 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-12  2:01 linux-next: manual merge of the drm-rust tree with the driver-core.current tree Stephen Rothwell
2025-09-12  7:57 ` Danilo Krummrich

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=anXu9ocZnLLP9PYr@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.