From: Yi Liu <yi.l.liu@intel.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org
Cc: "Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Clément Mathieu--Drif" <clement.mathieu--drif@eviden.com>,
"Zhenzhong Duan" <zhenzhong.duan@intel.com>
Subject: Re: Giving your own patches your Reviewed-by
Date: Wed, 12 Mar 2025 20:54:35 +0800 [thread overview]
Message-ID: <ca6ab1ec-4f30-4da7-ac08-3a514d8b4a02@intel.com> (raw)
In-Reply-To: <9329310c-bfad-44aa-a53a-87c1f39668a2@linaro.org>
On 2025/3/12 18:03, Philippe Mathieu-Daudé wrote:
> Hi Markus,
>
> (Cc'ing Yi, Clément and Zhenzhong for commit eda4c9b5b3c)
>
> On 12/3/25 10:45, Markus Armbruster wrote:
>> I stumbled over commits that carry the author's Reviewed-by.
>>
>> There may be cases where the recorded author isn't the lone author, and
>> the recorded author did some meaningful review of the patch's parts that
>> are not theirs. Mind that we do need all authors to provide their
>> Signed-off-by.
>>
>> When the only Signed-off-by is from the recorded author, and there's
>> also their Reviewed-by, the Reviewed-by is almost certainly bogus.
yeah, that might be sadly possible. :(
>>
>> Now, accidents happen, no big deal, etc., etc. I post this to hopefully
>> help reduce the accident rate :)
a dumb question. Where can I view this issue?
>>
>> Here's my quick & sloppy search for potentially problematic uses of
>> Reviewed-by:
>>
>> $ git-log --since 'two years ago' | awk -F: '/^commit / { commit=$0 }
>> /^Author: / { guy=$2 } /^ Reviewed-by: / { if ($2 == guy) { print
>> commit; print guy } }'
>
>
> Explaining some commits where I'm mentioned:
>
> commit 1e0d4eb4ee7c909323bffc39bc348eb3174b426b
> Author: Philippe Mathieu-Daudé <philmd@linaro.org>
> Date: Fri Apr 12 00:33:30 2024 -0700
>
> backends/tpm: Use qemu_hexdump_line() to avoid sprintf()
>
> sprintf() is deprecated on Darwin since macOS 13.0 / XCode 14.1.
> Using qemu_hexdump_line() both fixes the deprecation warning and
> simplifies the code base.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> [rth: Keep the linebreaks every 16 bytes]
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Message-ID: <20240412073346.458116-12-richard.henderson@linaro.org>
> [PMD: Rebased]
>
>
> I posted a patch with my S-o-b; Richard took it, improved and reposted
> it with his S-o-b; I reviewed Richard's changes (and eventually merged).
>
> commit 0fe4cac5dda1028c22ec3a6997e1b9155a768004
> Author: Peter Maydell <peter.maydell@linaro.org>
> Date: Mon Jul 17 18:29:40 2023 +0200
>
> target/mips: Avoid shift by negative number in page_table_walk_refill()
>
> Coverity points out that in page_table_walk_refill() we can
> shift by a negative number, which is undefined behaviour
> (CID 1452918, 1452920, 1452922). We already catch the
> negative directory_shift and leaf_shift as being a "bail
> out early" case, but not until we've already used them to
> calculated some offset values.
>
> The shifts can be negative only if ptew > 1, so make the
> bail-out-early check look directly at that, and only
> calculate the shift amounts and the offsets based on them
> after we have done that check. This allows
> us to simplify the expressions used to calculate the
> shift amounts, use an unsigned type, and avoids the
> undefined behaviour.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> [PMD: Check for ptew > 1, use unsigned type]
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> Message-Id: <20230717213504.24777-3-philmd@linaro.org>
>
> Peter posted the first patch, I reworked it and reposted,
> Peter reviewed my changes.
>
> commit c4380f7bcdcb68fdfca876db366782a807fab8f7
> Author: Richard Henderson <richard.henderson@linaro.org>
> Date: Thu Jan 18 21:06:30 2024 +0100
>
> target/arm: Create arm_cpu_mp_affinity
>
> Wrapper to return the mp affinity bits from the cpu.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Message-id: 20240118200643.29037-10-philmd@linaro.org
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>
> Is this workflow making sense and accepted? Otherwise what should
> we change? Maybe clarify along with the tags; or including all
> Message-Id could make this easier to track?
Commit eda4c9b5b3c is the similar case. Zhenzhong and Clément took
the patch from me and I was cced when Zhenzhong sent it out. I gave
my r-b after reviewing it.
--
Regards,
Yi Liu
next prev parent reply other threads:[~2025-03-12 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:45 Giving your own patches your Reviewed-by Markus Armbruster
2025-03-12 10:03 ` Philippe Mathieu-Daudé
2025-03-12 10:10 ` Markus Armbruster
2025-03-12 10:13 ` Daniel P. Berrangé
2025-03-12 12:54 ` Yi Liu [this message]
2025-03-13 6:45 ` CLEMENT MATHIEU--DRIF
2025-03-13 7:13 ` Markus Armbruster
2025-03-12 10:18 ` Philippe Mathieu-Daudé
2025-03-12 10:55 ` Markus Armbruster
2025-03-12 10:45 ` Daniel P. Berrangé
2025-03-12 10:56 ` Philippe Mathieu-Daudé
2025-03-13 1:21 ` bibo mao
2025-03-13 5:32 ` Markus Armbruster
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=ca6ab1ec-4f30-4da7-ac08-3a514d8b4a02@intel.com \
--to=yi.l.liu@intel.com \
--cc=akihiko.odaki@daynix.com \
--cc=armbru@redhat.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=maobibo@loongson.cn \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=zhenzhong.duan@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).