From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: Alice Ryhl <aliceryhl@google.com>,
Andreas Hindborg <a.hindborg@kernel.org>,
Andreas Hindborg <a.hindborg@samsung.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Matthew Maurer <mmaurer@google.com>
Subject: linux-next: manual merge of the rust tree with Linus' tree
Date: Mon, 16 Sep 2024 18:03:16 +1000 [thread overview]
Message-ID: <20240916180316.4516a56d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Hi all,
Today's linux-next merge of the rust tree got a conflict in:
rust/Makefile
between commit:
b8673d56935c ("rust: kbuild: fix export of bss symbols")
from Linus' tree and commit:
53bd83d95bb0 ("rust: cfi: add support for CFI_CLANG with Rust")
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/Makefile
index f168d2c98a15,dd76dc27d666..000000000000
--- a/rust/Makefile
+++ b/rust/Makefile
@@@ -305,7 -306,7 +306,7 @@@ $(obj)/bindings/bindings_helpers_genera
quiet_cmd_exports = EXPORTS $@
cmd_exports = \
$(NM) -p --defined-only $< \
- | awk '/ (T|R|D|B) / {printf "EXPORT_SYMBOL_RUST_GPL(%s);\n",$$3}' > $@
- | awk '$$2~/(T|R|D)/ && $$3!~/__cfi/ {printf "EXPORT_SYMBOL_RUST_GPL(%s);\n",$$3}' > $@
++ | awk '$$2~/(T|R|D|B)/ && $$3!~/__cfi/ {printf "EXPORT_SYMBOL_RUST_GPL(%s);\n",$$3}' > $@
$(obj)/exports_core_generated.h: $(obj)/core.o FORCE
$(call if_changed,exports)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-09-16 8:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 8:03 Stephen Rothwell [this message]
2024-09-16 8:12 ` linux-next: manual merge of the rust tree with Linus' tree Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2025-07-21 4:31 Stephen Rothwell
2025-07-21 8:23 ` Miguel Ojeda
2025-03-17 10:20 Stephen Rothwell
2025-03-17 19:37 ` Miguel Ojeda
2025-03-17 22:31 ` Stephen Rothwell
2025-03-17 22:35 ` Miguel Ojeda
2025-03-17 10:05 Stephen Rothwell
2025-03-17 19:36 ` Miguel Ojeda
2022-10-04 8:05 Stephen Rothwell
2022-09-12 7:24 Stephen Rothwell
2022-07-25 8:41 Stephen Rothwell
2022-07-25 8:52 ` Miguel Ojeda
2022-07-13 10:34 Stephen Rothwell
2022-07-13 10:50 ` Miguel Ojeda
2022-07-13 11:39 ` Peter Zijlstra
2022-07-15 1:13 ` Miguel Ojeda
2022-07-15 9:01 ` Peter Zijlstra
2022-07-15 11:01 ` Miguel Ojeda
2021-12-10 18:18 broonie
2021-11-03 3:19 Stephen Rothwell
2021-11-03 10:30 ` Miguel Ojeda
2021-11-03 21:01 ` Stephen Rothwell
2021-11-04 12:19 ` Miguel Ojeda
2021-11-04 20:31 ` Stephen Rothwell
2021-11-05 11:00 ` Miguel Ojeda
2021-07-19 6:16 Stephen Rothwell
2021-07-12 0:37 Stephen Rothwell
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=20240916180316.4516a56d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=a.hindborg@kernel.org \
--cc=a.hindborg@samsung.com \
--cc=aliceryhl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmaurer@google.com \
--cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox