From: Andy Whitcroft <apw@canonical.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: checkpatch should not complain about 'Suggested-by:'
Date: Mon, 23 Jul 2012 21:46:13 +0100 [thread overview]
Message-ID: <20120723204613.GD2491@dm> (raw)
In-Reply-To: <CA+8MBbLOi=GEkewV9RR40exw4KMP85LC8J3uNLQZQcKEhMWDCA@mail.gmail.com>
On Mon, Jul 23, 2012 at 10:26:29AM -0700, Tony Luck wrote:
> checkpatch just gave me:
>
> WARNING: Non-standard signature: Suggested-by:
Seems reasonable indeed.
> There are over 500 instances of 'Suggested-by:', and it seems
> to have some value in tracking history and awarding credit
> where it is due.
>
> "Reported-and-tested-by:" is also in regular use, but not
I really wish we didn't have this habit ...
Reported-fixed-tested-reviewed-and-signed-off-by: isn't easy to deal
with :/.
> in the list of "standard" signatures.
Will poke.
Cheers.
-apw
prev parent reply other threads:[~2012-07-23 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 17:26 checkpatch should not complain about 'Suggested-by:' Tony Luck
2012-07-23 20:46 ` Andy Whitcroft [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=20120723204613.GD2491@dm \
--to=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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).