From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrey Shvetsov <andrey.shvetsov@k2l.de>,
Christian Gromm <christian.gromm@microchip.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the staging tree
Date: Tue, 28 Nov 2017 20:41:39 +0100 [thread overview]
Message-ID: <20171128194139.GA2653@kroah.com> (raw)
In-Reply-To: <20171128081651.71a2e92a@canb.auug.org.au>
On Tue, Nov 28, 2017 at 08:16:51AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Commits
>
> 2525ef557c73 ("staging: most: update driver usage file")
> e7e3ce04588c ("staging: most: core: fix list traversing")
>
> are missing a Signed-off-by from their author.
Ugh, I missed that. Christian, please be more careful.
I need to set up a git hook for this :(
greg k-h
next prev parent reply other threads:[~2017-11-28 19:41 UTC|newest]
Thread overview: 19+ 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 [this message]
2017-11-28 22:59 ` Stephen Rothwell
2017-11-29 0:09 ` Michael Ellerman
2017-11-29 0:18 ` Stephen Rothwell
2018-02-23 9:17 ` Greg KH
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
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=20171128194139.GA2653@kroah.com \
--to=greg@kroah.com \
--cc=andrey.shvetsov@k2l.de \
--cc=christian.gromm@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.