From: Carlos Llamas <cmllamas@google.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Joe Perches <joe@perches.com>, Nam Cao <namcao@linutronix.de>,
apw@canonical.com, dwaipayanray1@gmail.com,
lukas.bulwahn@gmail.com, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH v2] checkpatch: add "Reported-and-tested-by:" tag
Date: Tue, 16 Jul 2024 22:44:32 +0000 [thread overview]
Message-ID: <Zpb30HMt6jXtonhr@google.com> (raw)
In-Reply-To: <CACT4Y+b0D-RmYznZ_+M98hDWiAZ-FG=eusagoeLGGQN4ZOB22w@mail.gmail.com>
On Tue, Jul 16, 2024 at 09:11:08AM +0200, Dmitry Vyukov wrote:
> On Tue, 16 Jul 2024 at 07:24, Carlos Llamas <cmllamas@google.com> wrote:
> >
> > 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
The number of patches with this tag is actually 2689. Sorry, I forgot to
add the --oneline option to my initial query.
>
> +syzkaller mailing list
>
> We can add whatever text you will say. What is the official position?
I don't know if there is an official position but IMO individual tags
are the safest option. This would even allow tools such as b4 to collect
the tags automatically. So splitting out 'Reported-and-tested-by:' seems
trivial enough?
Reported-by: syzbot+<context>
Tested-by: syzbot+<context>
next prev parent reply other threads:[~2024-07-16 22:44 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
2024-07-16 7:11 ` Dmitry Vyukov
2024-07-16 22:44 ` Carlos Llamas [this message]
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=Zpb30HMt6jXtonhr@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=syzkaller@googlegroups.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