From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Signed-off-by missing for commit in the ftrace tree
Date: Fri, 23 Jun 2023 17:36:57 +0900 [thread overview]
Message-ID: <20230623173657.44901820f684668d5b38da26@kernel.org> (raw)
In-Reply-To: <20230622184840.1dd4e945@gandalf.local.home>
On Thu, 22 Jun 2023 18:48:40 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 23 Jun 2023 08:35:50 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > Commits
> >
> > 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")
> >
> > are missing a Signed-off-by from their committer.
> >
>
> Masami, can you rebase and fix those commits?
Oops, yes.
Thanks!
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-06-23 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 22:35 linux-next: Signed-off-by missing for commit in the ftrace tree Stephen Rothwell
2023-06-22 22:48 ` Steven Rostedt
2023-06-23 8:36 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 21:28 Stephen Rothwell
2024-09-20 14:19 ` Steven Rostedt
2023-02-12 21:17 Stephen Rothwell
2023-02-13 0:35 ` Steven Rostedt
2023-02-13 12:33 ` Masami Hiramatsu
2022-12-12 21:52 Stephen Rothwell
2022-12-12 22:56 ` Steven Rostedt
2022-12-13 0:42 ` Stephen Rothwell
2022-12-13 1:11 ` Steven Rostedt
2021-10-26 21:17 Stephen Rothwell
2021-10-26 21:22 ` Steven Rostedt
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=20230623173657.44901820f684668d5b38da26@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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