* linux-next: manual merge of the rust tree with the mm-stable tree
@ 2025-05-26 7:37 Stephen Rothwell
2025-05-26 8:09 ` Miguel Ojeda
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2025-05-26 7:37 UTC (permalink / raw)
To: Miguel Ojeda, Andrew Morton
Cc: Alice Ryhl, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Hi all,
Today's linux-next merge of the rust tree got a conflict in:
rust/kernel/task.rs
between commit:
6acb75ad7b9e ("task: rust: rework how current is accessed")
from the mm-stable tree and commit:
f54c75033338 ("rust: task: add missing Markdown code spans and intra-doc links")
from the rust tree.
I fixed it up (the former removes the lines updated by the latter) 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-05-26 8:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-05-26 7:37 linux-next: manual merge of the rust tree with the mm-stable tree Stephen Rothwell
2025-05-26 8:09 ` Miguel Ojeda
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®