From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat•com>,
Jiri Olsa <jolsa@kernel•org>
Subject: linux-next: Signed-off-by missing for commits in the tip tree
Date: Mon, 17 Dec 2018 10:42:47 +1100 [thread overview]
Message-ID: <20181217104247.26549a16@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
Hi all,
Commit
5a0cb2ffce06 ("perf ordered_events: Add first_time() method")
is missing a Signed-off-by from its author.
Commits
a1dcb76e592a ("perf top: Move perf_top__reset_sample_counters() to after counts display")
ffec48b73449 ("perf top: Display slow reader warning when droping samples")
30eacd0f6c56 ("perf top: Save and display the drop count stats")
bdbc7bcf0f9a ("perf top: Drop samples which are behind the refresh rate")
2e86f646dd68 ("perf top: Set the 'session_done' volatile variable when exiting")
bc67057cab13 ("perf top: Use cond variable instead of a lock")
73df315a5120 ("perf top: Add processing thread")
f0a93bdc13e4 ("perf top: Move lost events warning to helpline")
f03b87dd0b44 ("perf top: Save and display the lost count stats")
4bc8acb7e06b ("perf ordered_events: Add private data member")
52ea6a5168fb ("perf ordered_events: Rework show_progress for __ordered_events__flush")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-12-16 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 23:42 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-12 11:27 linux-next: Signed-off-by missing for commits in the tip tree Stephen Rothwell
2018-01-24 22:29 Stephen Rothwell
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=20181217104247.26549a16@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=acme@redhat$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/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