[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <aNEdWOS8s6U0c5pz@finisterre.sirena.org.uk>
Date: Mon, 22 Sep 2025 10:56:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Boqun Feng <boqun.feng@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Matt Gilbride <mattgilbride@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Wedson Almeida Filho <wedsonaf@...il.com>
Subject: linux-next: manual merge of the char-misc tree with the tip tree
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
rust/helpers/helpers.c
between commit:
d9ea5a41cef80 ("rust: sync: Add memory barriers")
from the tip tree and commit:
eafedbc7c050c ("rust_binder: add Rust Binder driver")
from the char-misc 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/helpers/helpers.c
index 1c6096f53a6fe,8e8277bdddcae..0000000000000
--- a/rust/helpers/helpers.c
+++ b/rust/helpers/helpers.c
@@@ -7,9 -7,8 +7,10 @@@
* Sorted alphabetically.
*/
+#include "atomic.c"
#include "auxiliary.c"
+#include "barrier.c"
+ #include "binder.c"
#include "blk.c"
#include "bug.c"
#include "build_assert.c"
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists