[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250311201726.3f45cc67@canb.auug.org.au>
Date: Tue, 11 Mar 2025 20:17:26 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Miguel Ojeda <ojeda@...nel.org>, Dave Airlie <airlied@...hat.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Jocelyn Falempe
<jfalempe@...hat.com>, DRI <dri-devel@...ts.freedesktop.org>, Linux Kernel
Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the rust tree with the drm tree
Hi all,
Today's linux-next merge of the rust tree got a conflict in:
drivers/gpu/drm/drm_panic_qr.rs
between commit:
dbed4a797e00 ("drm/panic: Better binary encoding in QR code")
from the drm tree and commit:
fc2f191f850d ("panic_qr: use new #[export] macro")
from the rust tree.
I fixed it up (I guess - 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 drivers/gpu/drm/drm_panic_qr.rs
index 5d21f6d10bcb,ecd87e8ffe05..000000000000
--- a/drivers/gpu/drm/drm_panic_qr.rs
+++ b/drivers/gpu/drm/drm_panic_qr.rs
@@@ -27,7 -26,8 +27,7 @@@
//! * <https://github.com/erwanvivien/fast_qr>
//! * <https://github.com/bjguillot/qr>
- use kernel::str::CStr;
-use core::cmp;
+ use kernel::{prelude::*, str::CStr};
#[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd)]
struct Version(usize);
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists