Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760449AbcJ1OCW (ORCPT ); Fri, 28 Oct 2016 10:02:22 -0400 Received: from mail.fireflyinternet.com ([109.228.58.192]:61546 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759457AbcJ1OCU (ORCPT ); Fri, 28 Oct 2016 10:02:20 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Date: Fri, 28 Oct 2016 15:02:05 +0100 From: Chris Wilson To: Jani Nikula Cc: linux-kernel@vger.kernel.org, Andy Whitcroft , Joe Perches , intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] [PATCH] scripts/checkpatch: Check for Reviewed-by under --strict Message-ID: <20161028140205.GL29769@nuc-i3427.alporthouse.com> Mail-Followup-To: Chris Wilson , Jani Nikula , linux-kernel@vger.kernel.org, Andy Whitcroft , Joe Perches , intel-gfx@lists.freedesktop.org References: <20161028124944.17930-1-chris@chris-wilson.co.uk> <87y418k38p.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87y418k38p.fsf@intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1010 Lines: 20 On Fri, Oct 28, 2016 at 04:33:10PM +0300, Jani Nikula wrote: > On Fri, 28 Oct 2016, Chris Wilson wrote: > > Some subsystem polices have a strict requirement that every patch must > > have at least one reviewer before being approved for upstream. Since > > encouraging review is good policy (great review is even better policy!) > > enforce checking for a Reviewed-by when checkpath is run with --strict > > (or with --review). > > Hmm, do you imply the maintainer would have to add his Reviewed-by in > addition to Signed-off-by? I find that a bit too much (especially if you > intend to enforce this over at our corner of the kernel ;) I do believe we should be keeping the (our, my?) notion of review out of the signed-off-by tag (which imo is a legal statement about the provenance of a patch), and so yes we shouldn't be pushing patches that haven't gone through the rite of fire and been seconded by someone else. -Chris -- Chris Wilson, Intel Open Source Technology Centre