From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 22:41:37 +0200 [thread overview]
Message-ID: <20161027204137.ef6kxlzyvftcdomn@lukather> (raw)
In-Reply-To: <20161027104225.4f0f2774@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Hi Stephen,
On Thu, Oct 27, 2016 at 10:42:25AM +1100, Stephen Rothwell wrote:
> 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 :-)
Ok, that's actually the real question I had in mind, if you had a hook
I could use in order to avoid that kind of things in the future :)
I guess I have a new item on my todo list.
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-10-27 20:41 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
2016-10-27 20:41 ` Maxime Ripard [this message]
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=20161027204137.ef6kxlzyvftcdomn@lukather \
--to=maxime.ripard@free-electrons.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