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>
Subject: Re: linux-next: Signed-off-by missing for commits in the staging tree
Date: Thu, 11 Jan 2018 18:50:30 +0100 [thread overview]
Message-ID: <20180111175030.GA27093@kroah.com> (raw)
In-Reply-To: <20180110071830.6c7ccd1f@canb.auug.org.au>
On Wed, Jan 10, 2018 at 07:18:30AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Commits
>
> 97c6166001ef ("Staging: rtlwifi: Remove unused variable and the code")
> 357f862bd214 ("staging: comedi: adv_pci1760: fix typo in comments")
> 23cb746b5e9d ("staging: rtl8192u: Replace mdelay with msleep in rtl8192_usb_probe")
> beac4303532f ("Staging: vt6656: Fix unnecessary 'out of memory' message")
>
> are missing a Signed-off-by from their committer.
Crap, this has been a long month, sorry about that. I'll go work on
getting that git hook in place to prevent this from happening again...
greg k-h
next prev parent reply other threads:[~2018-01-11 17:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 20:18 linux-next: Signed-off-by missing for commits in the staging tree Stephen Rothwell
2018-01-11 17:50 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-27 21:16 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
2017-11-29 12:35 ` Stephen Rothwell
2017-11-29 12:42 ` Christian Gromm
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=20180111175030.GA27093@kroah.com \
--to=greg@kroah.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 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).