From: Pavel Machek <pavel@ucw.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
jgg@mellanox.com, Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Walleij <linus.walleij@linaro.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Require author Signed-off-by
Date: Wed, 11 Jul 2018 00:08:03 +0200 [thread overview]
Message-ID: <20180710220803.GA6387@amd> (raw)
In-Reply-To: <CAMuHMdVZae7Nb-Nr=f1uJD9ASxaio0Ob-5__FHzN=gEp9MSc+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
On Tue 2018-07-10 22:50:14, Geert Uytterhoeven wrote:
> Hi Pavel,
>
> On Tue, Jul 10, 2018 at 10:47 PM Pavel Machek <pavel@ucw.cz> wrote:
> > > Print an error if none of the Signed-off-by lines cover the patch
> > > author.
> >
> > Is it good idea? Signed-off-by system was _not_ meant to prevent
> > submission of third party patches.
>
> My main motivation is catching accidentally forgotten Sobs.
> It's still up to you to submit or accept a patch that triggers
> checkpatch errors.
Should it be at warning level, then, or explicitely saying this is
okay if you are not patch author?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-07-10 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 12:10 [PATCH] checkpatch: Require author Signed-off-by Geert Uytterhoeven
2018-07-10 14:33 ` Joe Perches
2018-07-10 15:07 ` Geert Uytterhoeven
2018-07-10 15:27 ` Joe Perches
2018-07-10 15:50 ` Geert Uytterhoeven
2018-07-10 16:22 ` Joe Perches
2018-07-10 20:47 ` Pavel Machek
2018-07-10 20:50 ` Geert Uytterhoeven
2018-07-10 22:08 ` Pavel Machek [this message]
2018-07-10 23:46 ` Joe Perches
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=20180710220803.GA6387@amd \
--to=pavel@ucw.cz \
--cc=apw@canonical.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=jgg@mellanox.com \
--cc=joe@perches.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yoshihiro.shimoda.uh@renesas.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