From: Steven Rostedt <rostedt@goodmis•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Masami Hiramatsu <mhiramat@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patches in the ftrace tree
Date: Fri, 27 Sep 2024 12:59:32 -0400 [thread overview]
Message-ID: <20240927125932.1cbf7e18@gandalf.local.home> (raw)
In-Reply-To: <20240927075439.2dac541e@canb.auug.org.au>
On Fri, 27 Sep 2024 07:54:39 +1000
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 1a41e44aaf63 ("tracepoint: Support iterating over tracepoints on modules")
> 3c842de2d916 ("sefltests/tracing: Add a test for tracepoint events on modules")
> 4ca74b253b11 ("tracepoint: Support iterating tracepoints in a loading module")
> 59c9f2923c04 ("tracing/fprobe: Support raw tracepoints on future loaded modules")
> 8e327678a908 ("kprobes: Remove obsoleted declaration for init_test_probes")
> c37e4bc7f70a ("tracing/fprobe: Support raw tracepoint events on modules")
>
Hmm, seems that Masami rebased his for-next branch. I just updated the
tracing for-next tree. They should have the same commits again.
-- Steve
next prev parent reply other threads:[~2024-09-27 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 21:54 linux-next: duplicate patches in the ftrace tree Stephen Rothwell
2024-09-27 16:59 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 22:40 Stephen Rothwell
2025-03-31 23:45 ` 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=20240927125932.1cbf7e18@gandalf.local.home \
--to=rostedt@goodmis$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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