From: Carlos Llamas <cmllamas@google.com>
To: Joe Perches <joe@perches.com>
Cc: Nam Cao <namcao@linutronix.de>,
apw@canonical.com, dwaipayanray1@gmail.com,
lukas.bulwahn@gmail.com, linux-kernel@vger.kernel.org,
Dmitry Vyukov <dvyukov@google.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] checkpatch: add "Reported-and-tested-by:" tag
Date: Tue, 16 Jul 2024 05:24:05 +0000 [thread overview]
Message-ID: <ZpYD9dDKYYK0BIA7@google.com> (raw)
In-Reply-To: <22344b13affea741ee41b0acb3c62884aac3e1bb.camel@perches.com>
On Sat, Apr 20, 2024 at 09:22:45AM -0700, Joe Perches wrote:
> On Sat, 2024-04-20 at 00:28 +0200, Nam Cao wrote:
> > The tag "Reported-and-tested-by:" is used all the time. Add this tag.
>
> General nack:
>
> I think that combined tags should be avoided
>
> see:
>
> Documentation/process/maintainer-tip.rst:Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
> Documentation/process/maintainer-tip.rst-they just complicate automated extraction of tags.
>
If combined tags are discouraged then syzbot should perhaps stop
suggesting the `Reported-and-tested-by:` tag? I would imagine this not
only applies to the tip tree and that other maintainers agree with not
using combined tags.
FWIW, this tag in particular though is quite popular:
$ git log --grep '^Reported-and-tested-by: ' origin/master |wc -l
82056
--
Carlos Llamas
next prev parent reply other threads:[~2024-07-16 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 22:28 [PATCH v2] checkpatch: add "Reported-and-tested-by:" tag Nam Cao
2024-04-20 16:22 ` Joe Perches
2024-07-16 5:24 ` Carlos Llamas [this message]
2024-07-16 7:11 ` Dmitry Vyukov
2024-07-16 22:44 ` Carlos Llamas
2024-07-17 10:24 ` Dmitry Vyukov
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=ZpYD9dDKYYK0BIA7@google.com \
--to=cmllamas@google.com \
--cc=apw@canonical.com \
--cc=dvyukov@google.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=namcao@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.