From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
qemu-devel@nongnu.org, ajones@ventanamicro.com,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 2/2] system/vl.c: parse all -accel options
Date: Mon, 1 Jul 2024 18:43:40 +0200 [thread overview]
Message-ID: <CABgObfZzVN+CuCpYOpLqYERht_ipk4Xv_oydWi59WytyQtddsA@mail.gmail.com> (raw)
In-Reply-To: <5e0c57ef-d06d-4cdc-8d5b-3adec8263c5f@linaro.org>
On Mon, Jul 1, 2024 at 4:34 PM Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
In principle, a Reviewed-by tag is just stating that you don't know of
any issues that would prevent the patch being included. However, as a
frequent participant to the project, your Reviewed-by tag carries some
weight and, to some extent, it is also a statement that you understand
the area being modified. A Reviewed-by from an experienced
contributor may even imply that you could take the patch in one of
your pull requests. (*) That makes it even more important to
understand the area.
I would expect that anyone with an understanding of command line
parsing would know 1) what -accel kvm -accel tcg does, and 2) what
.merge_lists does; and this would be enough to flag an issue
preventing the patch from being included.
To be clear, I don't expect reviews to be perfect. But in this case
I'm speaking up because the patch is literally a one line declarative
change, and the only way to say "I've reviewed it" is by understanding
the deeper effects of that line.
Also, I think it's fair that the submitter didn't spot the problem;
it's okay to send out broken patches, that's part of the learning
experience. :)
Paolo
(*) as opposed to Acked-by, where your review probably has been more
conceptual than technical, and that you don't really want to take the
patch in a pull request.
Paolo
next prev parent reply other threads:[~2024-07-01 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 13:30 [PATCH 0/2] system/vl.c: parse all '-accel' opts Daniel Henrique Barboza
2024-07-01 13:30 ` [PATCH 1/2] system/vl.c: do not allow mixed -accel opts Daniel Henrique Barboza
2024-07-01 15:23 ` Richard Henderson
2024-07-01 15:53 ` Daniel Henrique Barboza
2024-07-01 16:23 ` Paolo Bonzini
2024-07-01 13:30 ` [PATCH 2/2] system/vl.c: parse all -accel options Daniel Henrique Barboza
2024-07-01 14:34 ` Philippe Mathieu-Daudé
2024-07-01 16:43 ` Paolo Bonzini [this message]
2024-07-01 19:47 ` Philippe Mathieu-Daudé
2024-07-04 11:01 ` Alex Bennée
2024-07-01 16:31 ` [PATCH 0/2] system/vl.c: parse all '-accel' opts Paolo Bonzini
2024-07-01 17:20 ` Daniel Henrique Barboza
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=CABgObfZzVN+CuCpYOpLqYERht_ipk4Xv_oydWi59WytyQtddsA@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=ajones@ventanamicro.com \
--cc=dbarboza@ventanamicro.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).