From: "Tobin C. Harding" <me@tobin.cc>
To: Joe Perches <joe@perches.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Jani Nikula <jani.nikula@linux.intel.com>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
Jonathan Cameron <jic23@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Niklas Cassel <niklas.cassel@linaro.org>
Subject: Re: [PATCH v2] docs: Clarify the usage and sign-off requirements for Co-developed-by
Date: Fri, 22 Mar 2019 10:29:25 +1100 [thread overview]
Message-ID: <20190321232925.GA17705@eros.localdomain> (raw)
In-Reply-To: <0cc879a63943b57b62caddce6866b83a14b42c14.camel@perches.com>
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@kernel.org>
Catches missing SOB of co-developer.
Hope this helps,
Tobin.
prev parent reply other threads:[~2019-03-21 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 18:43 [PATCH v2] docs: Clarify the usage and sign-off requirements for Co-developed-by Sean Christopherson
2019-03-21 19:14 ` Greg Kroah-Hartman
2019-03-21 19:23 ` Sean Christopherson
2019-03-21 22:47 ` Joe Perches
2019-03-21 23:29 ` Tobin C. Harding [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190321232925.GA17705@eros.localdomain \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=jic23@kernel.org \
--cc=joe@perches.com \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox