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: Signed-off-by missing for commit in the ftrace tree
Date: Mon, 12 Dec 2022 17:56:42 -0500 [thread overview]
Message-ID: <20221212175642.77cba577@gandalf.local.home> (raw)
In-Reply-To: <20221213085200.772ddd94@canb.auug.org.au>
On Tue, 13 Dec 2022 08:52:00 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Commits
>
> fff1787adaee ("trace/kprobe: remove duplicated calls of ring_buffer_event_data")
> 8c2b99790196 ("tracing: docs: Update histogram doc for .percent/.graph and 'nohitcount'")
> ccf47f5cc4ce ("tracing: Add nohitcount option for suppressing display of raw hitcount")
> a2c54256dec7 ("tracing: Add .graph suffix option to histogram value")
> abaa5258ce5e ("tracing: Add .percent suffix option to histogram values")
> 5f2e094ed259 ("tracing: Allow multiple hitcount values in histograms")
>
> are missing a Signed-off-by from their committers.
>
Bah, not sure how this happened. I thought I pulled these patches directly
from Masami. Does a rebase change the committer tags? As I probably rebased
them on top of my branch.
-- Steve
next prev parent reply other threads:[~2022-12-12 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 21:52 Stephen Rothwell
2022-12-12 22:56 ` Steven Rostedt [this message]
2022-12-13 0:42 ` Stephen Rothwell
2022-12-13 1:11 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 21:28 Stephen Rothwell
2024-09-20 14:19 ` Steven Rostedt
2023-06-22 22:35 Stephen Rothwell
2023-06-22 22:48 ` Steven Rostedt
2023-06-23 8:36 ` Masami Hiramatsu
2023-02-12 21:17 Stephen Rothwell
2023-02-13 0:35 ` Steven Rostedt
2023-02-13 12:33 ` Masami Hiramatsu
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=20221212175642.77cba577@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.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
all inboxes | Powered by JetHome®