public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Rostedt <rostedt@goodmis•org>,
	Masami Hiramatsu <mhiramat@kernel•org>
Cc: Akanksha J N <akanksha@linux•ibm.com>,
	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: Fri, 14 Jul 2023 14:54:04 +1000	[thread overview]
Message-ID: <20230714145404.115c7be1@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

Hi all,

The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):

  e46ad59233cf ("selftests/ftrace: Add new test case which checks for optimized probes")
  bd2cdc432190 ("selftests/ftrace: Add new test case which adds multiple consecutive probes in a function")

These are commits

  5985329c7073 ("selftests/ftrace: Add new test case which checks for optimized probes")
  cf9071dd46e7 ("selftests/ftrace: Add new test case which adds multiple consecutive probes in a function")

in Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-07-14  4:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  4:54 Stephen Rothwell [this message]
2023-07-14  8:31 ` linux-next: duplicate patches in the ftrace tree Masami Hiramatsu
  -- strict thread matches above, loose matches on Subject: below --
2025-03-31 22:40 Stephen Rothwell
2025-03-31 23:45 ` Steven Rostedt
2024-09-26 21:54 Stephen Rothwell
2024-09-27 16:59 ` Steven Rostedt
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=20230714145404.115c7be1@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akanksha@linux$(echo .)ibm.com \
    --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