From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Rostedt <rostedt@goodmis•org>,
Masami Hiramatsu <mhiramat@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the ftrace tree
Date: Tue, 1 Apr 2025 09:40:14 +1100 [thread overview]
Message-ID: <20250401094014.4134abe1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
0e5d1a4b22bc ("ring-buffer: Remove the unused variable bmeta")
186a3d01d596 ("module: Add module_for_each_mod() function")
34c9862b1833 ("tracing: Skip update_last_data() if cleared and remove active check for save_mod()")
45be9d6a4e4c ("ring-buffer: Use kaslr address instead of text delta")
47d1b7233ae8 ("ring-buffer: Add ring_buffer_meta_scratch()")
4cb6fa440707 ("tracing: Show module names and addresses of last boot")
7f335d104d30 ("ring-buffer: Add buffer meta data for persistent ring buffer")
9042bbf70203 ("tracing: Freeable reserved ring buffer")
aad5fa4e9de1 ("mm/memblock: Add reserved memory release function")
bab85a646dd9 ("tracing: Show last module text symbols in the stacktrace")
c6a1b7c2e58d ("tracing: Update modules to persistent instances when loaded")
dca91c1c5468 ("tracing: Have persistent trace instances save module addresses")
dfc0b3249550 ("tracing: Initialize scratch_size to zero to prevent UB")
e39a2f30d23c ("tracing: Fix a compilation error without CONFIG_MODULES")
f20423262b36 ("tracing: Use _text and the kernel offset in last_boot_info")
f5d0a66ca482 ("tracing: Have persistent trace instances save KASLR offset")
ff700de3978f ("ring-buffer: Fix bytes_dropped calculation issue")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-03-31 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 22:40 Stephen Rothwell [this message]
2025-03-31 23:45 ` linux-next: duplicate patches in the ftrace tree Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2024-09-26 21:54 Stephen Rothwell
2024-09-27 16:59 ` Steven Rostedt
2023-07-14 4:54 Stephen Rothwell
2023-07-14 8:31 ` Masami Hiramatsu
2023-04-03 4:51 Stephen Rothwell
2023-04-03 20:08 ` Ross Zwisler
2023-02-24 5:34 Stephen Rothwell
2023-02-24 7:04 ` Masami Hiramatsu
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=20250401094014.4134abe1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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