From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jonathan Corbet <corbet@lwn.net>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Tobin C . Harding" <me@tobin.cc>,
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: [PATCH v5 0/2] docs: checkpatch: improve handling of Co-developed-by
Date: Fri, 22 Mar 2019 14:11:35 -0700 [thread overview]
Message-ID: <20190322211137.18241-1-sean.j.christopherson@intel.com> (raw)
The recently introduced Co-developed-by: tag has seen a spate of
improper usage, likely because the tag is less intuitive and slightly
more complex than most other tags. Rework the documentation to be more
explicit in how Co-developed-by: is intended to be used, add examples
in the docs, and add logic to checkpatch to reinforce proper usage.
v1: https://lkml.kernel.org/r/20190320151140.32432-1-sean.j.christopherson@intel.com
v2: https://lkml.kernel.org/r/20190321184316.8525-1-sean.j.christopherson@intel.com
Rewrite the blurb to state standard sign-off procedure should be
followed as opposed to dictating the original author's SOB be last.
v3: https://lkml.kernel.org/r/20190321200103.9333-1-sean.j.christopherson@intel.com
Update a similar blurb in Documentation/process/5.Posting.rst
v4: https://lkml.kernel.org/r/20190322155735.13954-1-sean.j.christopherson@intel.com
Rework the blurbs to avoid use of the word "original" [Tobin]
v5: Add checkpatch warnings [Joe]
Fix a spelling error [Niklas]
Sean Christopherson (2):
docs: Clarify the usage and sign-off requirements for Co-developed-by
checkpatch: Warn on improper usage of Co-developed-by
Documentation/process/5.Posting.rst | 10 +++--
Documentation/process/submitting-patches.rst | 40 +++++++++++++++++---
scripts/checkpatch.pl | 18 +++++++++
3 files changed, 59 insertions(+), 9 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-22 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 21:11 Sean Christopherson [this message]
2019-03-22 21:11 ` [PATCH v5 1/2] docs: Clarify the usage and sign-off requirements for Co-developed-by Sean Christopherson
2019-03-23 2:00 ` Tobin C. Harding
2019-03-25 16:31 ` Jonathan Corbet
2019-03-25 16:40 ` Joe Perches
2019-03-25 16:45 ` Jonathan Corbet
2019-03-22 21:11 ` [PATCH v5 2/2] checkpatch: Warn on improper usage of Co-developed-by Sean Christopherson
2019-03-23 2:01 ` Tobin C. Harding
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=20190322211137.18241-1-sean.j.christopherson@intel.com \
--to=sean.j.christopherson@intel.com \
--cc=apw@canonical.com \
--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=me@tobin.cc \
--cc=niklas.cassel@linaro.org \
--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
all inboxes | Powered by JetHome®