[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190321232925.GA17705@eros.localdomain>
Date: Fri, 22 Mar 2019 10:29:25 +1100
From: "Tobin C. Harding" <me@...in.cc>
To: Joe Perches <joe@...ches.com>
Cc: Sean Christopherson <sean.j.christopherson@...el.com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@...aro.org>,
Jonathan Cameron <jic23@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Niklas Cassel <niklas.cassel@...aro.org>
Subject: Re: [PATCH v2] docs: Clarify the usage and sign-off requirements for
Co-developed-by
On Thu, Mar 21, 2019 at 03:47:26PM -0700, Joe Perches wrote:
> On Thu, 2019-03-21 at 12:23 -0700, Sean Christopherson wrote:
> > On Thu, Mar 21, 2019 at 11:43:16AM -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
>
> While I still think co-developed-by: is unnecessary and
> almost none of the existing uses of this have this
> sequence of "Co-developed-by: <name/email>" followed directly
> by "Signed-off-by: <same name/email>", here's a possible
> checkpatch addition for it.
Tested-by: Tobin C. Harding <tobin@...nel.org>
Catches missing SOB of co-developer.
Hope this helps,
Tobin.
Powered by blists - more mailing lists