From: Himanshu Jha <himanshujha199640@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
joe@perches.com, gregkh@linuxfoundation.org, apw@canonical.com,
linux-kernel@vger.kernel.org, niklas.cassel@linaro.org,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] checkpatch: add Co-developed-by to signature tags
Date: Sat, 15 Dec 2018 02:28:00 +0530 [thread overview]
Message-ID: <20181214205800.GA22639@himanshu-Vostro-3559> (raw)
In-Reply-To: <20181214121634.1157f2302c8ba1825fc03ad2@linux-foundation.org>
On Fri, Dec 14, 2018 at 12:16:34PM -0800, Andrew Morton wrote:
> On Fri, 14 Dec 2018 18:35:28 +0100 Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org> wrote:
>
> > As per Documentation/process/submitting-patches, Co-developed-by is a
> > valid signature.
> >
>
> I'm with Joe - I find this tag kinda useless and duplicative. But whatever.
I'm fine either way, just the problem is:
Co-developed-by Vs Co-Developed-by
with checkpatch spitting out that it is not a valid signature.
In the end, I can completely remove the tag from docs if it is useless
and duplicative.
--
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology
next prev parent reply other threads:[~2018-12-14 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:35 [PATCH 0/2] Fix Co-Developed-by Jorge Ramirez-Ortiz
2018-12-14 17:35 ` [PATCH 1/2] docs: fix Co-Developed-by docs Jorge Ramirez-Ortiz
2018-12-14 18:12 ` Himanshu Jha
2018-12-14 17:35 ` [PATCH 2/2] checkpatch: add Co-developed-by to signature tags Jorge Ramirez-Ortiz
2018-12-14 20:16 ` Andrew Morton
2018-12-14 20:58 ` Himanshu Jha [this message]
2018-12-15 17:45 ` Joe Perches
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=20181214205800.GA22639@himanshu-Vostro-3559 \
--to=himanshujha199640@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.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 \
/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;
as well as URLs for NNTP newsgroup(s).