From: Masami Hiramatsu (Google) <mhiramat@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Shuah Khan <shuah@kernel•org>,
Steven Rostedt <rostedt@goodmis•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patch in the kselftest tree
Date: Thu, 20 Nov 2025 14:42:01 +0900 [thread overview]
Message-ID: <20251120144201.5e911aed3cfd12fa3068bdea@kernel.org> (raw)
In-Reply-To: <20251120162349.0c84ab13@canb.auug.org.au>
On Thu, 20 Nov 2025 16:23:49 +1100
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> The following commit is also in the ftrace tree as a different commit
> (but the same patch):
>
> a2f7990d3309 ("selftests: tracing: Update fprobe selftest for ftrace based fprobe")
>
> This is commit
>
> 5810077b5219 ("selftests: tracing: Update fprobe selftest for ftrace based fprobe")
>
> in the ftrace tree.
Ah, sorry I should remove this patch from my tree.
Thanks,
>
> --
> Cheers,
> Stephen Rothwell
--
Masami Hiramatsu (Google) <mhiramat@kernel•org>
next prev parent reply other threads:[~2025-11-20 5:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 5:23 linux-next: duplicate patch in the kselftest tree Stephen Rothwell
2025-11-20 5:42 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-02 6:36 Stephen Rothwell
2025-07-02 15:57 ` Shuah Khan
2025-07-02 18:06 ` Andrew Morton
2024-04-15 4:43 Stephen Rothwell
2024-04-16 23:54 ` Shuah Khan
2023-10-17 4:03 Stephen Rothwell
2023-10-17 15:18 ` Shuah Khan
2023-10-18 10:44 ` Ingo Molnar
2023-06-05 23:02 Stephen Rothwell
2023-06-05 23:21 ` Shuah Khan
2023-03-29 1:23 Stephen Rothwell
2023-04-23 16:06 ` Shuah Khan
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=20251120144201.5e911aed3cfd12fa3068bdea@kernel.org \
--to=mhiramat@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shuah@kernel$(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