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>
Subject: linux-next: Signed-off-by missing for commits in the tip tree
Date: Thu, 25 Jan 2018 09:29:59 +1100 [thread overview]
Message-ID: <20180125092959.3da36eec@canb.auug.org.au> (raw)
Hi all,
Commits
a5d8ae1255fb ("perf vendor events intel: Update Broadwell events to V22")
theough
553f486f5129 ("perf vendor events intel: Update IvyTown files to V20")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2018-01-24 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 22:29 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-16 23:42 linux-next: Signed-off-by missing for commits in the tip tree Stephen Rothwell
2019-04-12 11:27 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=20180125092959.3da36eec@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).