Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp859260img; Fri, 22 Mar 2019 10:04:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqy7S/CzI4gSsRq1QukM8AU/ZontK73oWn3tfTmaP+e9xcpVUqud3Fdoo39dMDpd5/iGZo8A X-Received: by 2002:a17:902:7590:: with SMTP id j16mr10675830pll.304.1553274243348; Fri, 22 Mar 2019 10:04:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553274243; cv=none; d=google.com; s=arc-20160816; b=wrPrRPtF7nwhybdKjHCMI+hqsKUm+/3t1/t8SyKP2rATx6T1BMJRofuFexOxFIAo2K RZfKt5KKXjJQXMFFU5WM5dQ95XgzqRLNBBnvM8RNca1cwgH9ponvUtYVrwLT1g3dcSJu bzSG7mKV7BKM0vY0+/T0r2oDJysChEE97uaK+05L+cwTGVvflLm3/28sVIzvrT9C6t51 TwFhTquXwFslLRdL4NYjXyPB+Xdz+d5eCspiGUXgkAZ09w5Rf66kmiXbyMT68YlLQPk5 fIFA5daYFhkMYDp+8KrO5qQfryd8TlC4KqeUWSZPnZPomL16IRhUNOl6t/hOb3wRbzR5 wdvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=+4wjbitE/yPu52TlGGyZW3CTJOXUooytplvN+dOhVuk=; b=y2c6qHsa46QMLuaDqpW4qe84ZAPLbnUfWgturXZwJyC2HVGbphpn1hFxPrL3QuirUD 5rkvsFNji7brLfVx2KKDFyQuKfipWGgQvjUkMGpDgUytHCKgexDiwtV6Lvd3Q1kwLqqP rApwPQRzJC00H8paCkRXmwvUbRwd9l+1X76s7y3+o1CpY6FLeDh+aJN8vTb3eH9XjPOY ZEOY59O7nh1S1k1nw7euk/u3JtWChQmdy5usq1B2RqodMGL70mlfXdSMDEd5ywE2CZ1o R3b7YAPdZl0zp6AZRHnqihCNvGvOCYvlf/aP0nDqZFWWjYXajFb/KsyrhGBU2D1DkGuy efng== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p4si7155496pgb.558.2019.03.22.10.03.47; Fri, 22 Mar 2019 10:04:03 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728029AbfCVRDM (ORCPT + 99 others); Fri, 22 Mar 2019 13:03:12 -0400 Received: from smtprelay0250.hostedemail.com ([216.40.44.250]:56328 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727105AbfCVRDM (ORCPT ); Fri, 22 Mar 2019 13:03:12 -0400 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay02.hostedemail.com (Postfix) with ESMTP id A824C613F; Fri, 22 Mar 2019 17:03:10 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::::::,RULES_HIT:41:355:379:599:968:988:989:1260:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1777:1792:2198:2199:2393:2559:2562:2828:3138:3139:3140:3141:3142:3353:3622:3865:3866:3867:3868:3870:3871:3872:3874:4321:5007:7808:7875:8660:10004:10400:10848:11232:11658:11914:12109:12219:12740:12760:12895:13069:13148:13230:13255:13311:13357:13439:14096:14097:14659:14721:21080:21627:30045:30054:30074:30091,0,RBL:47.151.153.53:@perches.com:.lbl8.mailshell.net-62.8.0.100 64.201.201.201,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:neutral,Custom_rules:0:0:0,LFtime:29,LUA_SUMMARY:none X-HE-Tag: heat55_1b77e98677f4d X-Filterd-Recvd-Size: 2496 Received: from XPS-9350.home (unknown [47.151.153.53]) (Authenticated sender: joe@perches.com) by omf15.hostedemail.com (Postfix) with ESMTPA; Fri, 22 Mar 2019 17:03:08 +0000 (UTC) Message-ID: <0f4538aa6a91c071f6e590c2d3f60a474b14fab5.camel@perches.com> Subject: Re: [PATCH v4] docs: Clarify the usage and sign-off requirements for Co-developed-by From: Joe Perches To: Sean Christopherson , Jonathan Corbet Cc: 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 Date: Fri, 22 Mar 2019 10:03:07 -0700 In-Reply-To: <20190322155735.13954-1-sean.j.christopherson@intel.com> References: <20190322155735.13954-1-sean.j.christopherson@intel.com> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.30.1-1build1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.