From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Gromm <christian.gromm@microchip.com>
Cc: Greg KH <greg@kroah.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrey Shvetsov <andrey.shvetsov@k2l.de>
Subject: Re: linux-next: Signed-off-by missing for commits in the staging tree
Date: Wed, 29 Nov 2017 23:24:46 +1100 [thread overview]
Message-ID: <20171129232446.5b268bcb@canb.auug.org.au> (raw)
In-Reply-To: <ece95101-65e9-9008-1e24-f9b76db13a98@microchip.com>
Hi Christian,
On Wed, 29 Nov 2017 09:44:44 +0100 Christian Gromm <christian.gromm@microchip.com> wrote:
>
> Hmm, am I missing something here? I have it in.
> Here are copies of the patches in question and both have
> a "Signed-off-by" line in.
According to the From: line in the body of these emails, the author of
this patch is Andrey Shvetsov <andrey.shvetsov@k2l.de>, and there is no
Signed-off-by line from Andrey.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-11-29 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 21:16 linux-next: Signed-off-by missing for commits in the staging tree Stephen Rothwell
2017-11-28 19:41 ` Greg KH
2017-11-28 22:59 ` Stephen Rothwell
2017-11-29 0:09 ` Michael Ellerman
2017-11-29 0:18 ` Stephen Rothwell
2017-11-29 8:44 ` Christian Gromm
2017-11-29 9:14 ` Greg KH
2017-11-29 9:25 ` Christian Gromm
2017-11-29 9:32 ` Greg KH
2017-11-29 12:24 ` Stephen Rothwell [this message]
2017-11-29 12:35 ` Stephen Rothwell
2017-11-29 12:42 ` Christian Gromm
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 20:18 Stephen Rothwell
2018-01-11 17:50 ` Greg KH
2017-09-18 21:54 Stephen Rothwell
2017-09-19 6:09 ` Greg KH
2017-09-19 15:34 ` Tobin Harding
2017-09-19 15:50 ` Tobin Harding
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=20171129232446.5b268bcb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrey.shvetsov@k2l.de \
--cc=christian.gromm@microchip.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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