public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: bad commit in the sunxi tree
Date: Thu, 27 Oct 2016 10:42:25 +1100	[thread overview]
Message-ID: <20161027104225.4f0f2774@canb.auug.org.au> (raw)
In-Reply-To: <20161025094409.hhf5rg3gbzaryjom@lukather>

Hi Maxime,

On Tue, 25 Oct 2016 11:44:09 +0200 Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>
> On Tue, Oct 25, 2016 at 09:22:55AM +1100, Stephen Rothwell wrote:
> > Hi Maxime,
> > 
> > In today's sunxi tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next)
> > I noticed that commit
> > 
> >   3861b711f8b5 ("ARM: sun5i: chip: add a node for the w1 gpio controller")
> > 
> > has no Signed-off-by from its committer.  
> 
> Thanks, this has been fixed.
> 
> Just out of curiosity, what command do you run to catch this?

None :-)  I look at the differences in each tree as I fetch it and
just happen to notice some of these sometimes.  I should have a git
hook to check that there is a Signed-off-by for the author and
committer, but I would have to invest some time to figure out how :-)

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2016-10-26 23:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 22:22 linux-next: bad commit in the sunxi tree Stephen Rothwell
2016-10-25  9:44 ` Maxime Ripard
2016-10-26 23:42   ` Stephen Rothwell [this message]
2016-10-27 20:41     ` Maxime Ripard
2016-10-31  2:59       ` Michael Ellerman
2016-10-31 14:57         ` 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=20161027104225.4f0f2774@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    /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