From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 47FD3C43381 for ; Fri, 22 Mar 2019 17:03:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2264F2190A for ; Fri, 22 Mar 2019 17:03:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728175AbfCVRDM (ORCPT ); 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-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.