Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp868442img; Fri, 22 Mar 2019 10:15:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqyrxgfJSZPrtVKtG6MEUCgrTmn4I9gaaAWo4/Za+Oc3Q59iRGUriXRhukn2UxLgDnlRkG3Y X-Received: by 2002:a63:c06:: with SMTP id b6mr10005234pgl.440.1553274900970; Fri, 22 Mar 2019 10:15:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553274900; cv=none; d=google.com; s=arc-20160816; b=UC2R1rHKr6fGLLlqFvw6LOTrLY4+7PCJyvlxPaZUAHkpMvqgaLJjHiuKMEZ97Eo/NZ Zv6oMy/qPLbbt6Aj/7Xks35Kgc4XuV0r5snXB9/kP4mzrBpBrNNShNPC1f0RpBx9GPvQ 3bsmId6JuRlWWFLtHMy0CDK52p5xmcmteiHCpALva2VtL/11fuYqdUuhIIGmhQTj33hK eKKQOyPnJS6ppZseq8xy/Ty4PsaaS4G21DOJe6uJYo8z7JWKjZVrz0s4KoVNG74/ufRP hdaP1ViOJmnnQwJdqCVljNcaVab32OUiZFbPEbPvO7Ckz3xSqGrnUzX9ZQN4rHXNogU7 0Bfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=V2m1ztPn6flSRKnU38oCmj1yk0NKHviKpfD0exzDETI=; b=JaCT3iJtEgOSh/5+ZhWxz89eup2RV7OM4cWQPvFeUNArRA5lEee1cn5zhqFIpwCTnE 0fgaXIiHXXMu7YyGJBosjM46PsduyHYmjzFZaoqTEV0etznkfFu3glI+6zYXg9x5lW8v 78TXCxhS3czWjD0nvCD+SrSeLnW9xCJmDaRW3WgdZGBeV1BI37zX0uoQx2RMstDgcbAt CxGeSLM2+o7oSpA86HpyCNDODGUJXzLRZmXZoELYoZBmir9hBW2fSbn3+2huw4WuGyLR 1e7SH1VgZZ2yHWtYw6TnRLJjZXx5HNBN8iVBpDqlwnuJnQXYE86v2jN5aFaSlbleBecd Bcaw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 138si6266247pfa.199.2019.03.22.10.14.42; Fri, 22 Mar 2019 10:15:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728686AbfCVRNr (ORCPT + 99 others); Fri, 22 Mar 2019 13:13:47 -0400 Received: from mga18.intel.com ([134.134.136.126]:62824 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728091AbfCVRNq (ORCPT ); Fri, 22 Mar 2019 13:13:46 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2019 10:13:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,256,1549958400"; d="scan'208";a="331088388" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.181]) by fmsmga005.fm.intel.com with ESMTP; 22 Mar 2019 10:13:44 -0700 Date: Fri, 22 Mar 2019 10:13:44 -0700 From: Sean Christopherson To: Joe Perches Cc: Jonathan Corbet , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, "Tobin C . Harding" , Thomas Gleixner , Jani Nikula , Jorge Ramirez-Ortiz , Jonathan Cameron , Greg Kroah-Hartman , Niklas Cassel Subject: Re: [PATCH v4] docs: Clarify the usage and sign-off requirements for Co-developed-by Message-ID: <20190322171344.GC12666@linux.intel.com> References: <20190322155735.13954-1-sean.j.christopherson@intel.com> <0f4538aa6a91c071f6e590c2d3f60a474b14fab5.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0f4538aa6a91c071f6e590c2d3f60a474b14fab5.camel@perches.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 22, 2019 at 10:03:07AM -0700, Joe Perches wrote: > On Fri, 2019-03-22 at 08:57 -0700, Sean Christopherson wrote: > > The documentation for Co-developed-by is a bit light on details, e.g. it > > doesn't explicitly state that: > > > > - Multiple Co-developed-by tags are perfectly acceptable > > - Co-developed-by and Signed-off-by must be paired together > > - SOB ordering should still follow standard sign-off procedure > > > > Lack of explicit direction has resulted in developers taking a variety > > of approaches, often lacking any intent whatsoever, e.g. scattering SOBs > > willy-nilly, collecting them all at the end or the beginning, etc... > > Tweak the wording to make it clear that multiple co-authors are allowed, > > and document the expectation that standard sign-off procedures are to > > be followed. > > > > The use of "original author" has also led to confusion as many patches > > don't have just one "original" author, e.g. when multiple developers > > are involved from the genesis of the patch. Remove all usage of > > "original" and instead call out that Co-developed-by is simply a way to > > provide attribution in addition to the From tag, i.e. neither tag is > > intended to imply anything with regard to who did what. > > > > Provide examples to (hopefully) eliminate any ambiguity. > > Please add the checkpatch bit to this at the same time. Doh, spaced on that. I'll wait for additional feedback before sending v5.