From: "Daniel P. Berrangé" <berrange@redhat.com>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, mst@redhat.com, chao.liu@processmission.com
Subject: Re: [PATCH] scripts/checkpatch: warn on duplicate trailers and self-review
Date: Thu, 3 Sep 2026 13:01:11 +0100 [thread overview]
Message-ID: <aplhh_7vb-v5MTT2@redhat.com> (raw)
In-Reply-To: <20260727161157.2112984-1-marcandre.lureau@redhat.com>
On Mon, Jul 27, 2026 at 08:11:56PM +0400, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Detect two common trailer mistakes:
>
> - Duplicate trailers: any trailer (Signed-off-by, Fixes, Resolves,
> Cc, etc.) appearing more than once with the same value in a commit
> message.
>
> - Self-review: a Reviewed-by, Tested-by, or Acked-by tag from the
> same person as the patch author, which provides no independent
> review value.
That could happen if someone starts a patch, then someone else
takes over and does more, then the original author tests/reviews
the result. Since this is merely a warning though, I think that
its fine to ignore.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> scripts/checkpatch.pl | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-09-03 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 16:11 [PATCH] scripts/checkpatch: warn on duplicate trailers and self-review marcandre.lureau
2026-08-20 12:42 ` Marc-André Lureau
2026-09-03 12:01 ` Daniel P. Berrangé [this message]
2026-09-03 12:01 ` Paolo Bonzini
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=aplhh_7vb-v5MTT2@redhat.com \
--to=berrange@redhat.com \
--cc=chao.liu@processmission.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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 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.