From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the sound-asoc tree
Date: Fri, 9 Aug 2019 07:43:25 +1000 [thread overview]
Message-ID: <20190809074325.65a72962@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
Hi all,
Commit
c42d8cbee4c7 ("Merge branches from Takashi to ease Skylake development.")
is missing a Signed-off-by from its author and committer.
Despite what the commit message says, this is not a merge commit.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-08 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 21:43 Stephen Rothwell [this message]
2019-08-08 22:12 ` linux-next: Signed-off-by missing for commit in the sound-asoc tree Mark Brown
2019-08-08 22:23 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2018-12-06 21:01 Stephen Rothwell
2018-03-19 8:12 Stephen Rothwell
2018-03-19 8:20 ` Mark Brown
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=20190809074325.65a72962@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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