From: Igor Mammedov <imammedo@redhat.com>
To: Liav Albani <liavalb@gmail.com>
Cc: ani@anisinha.ca, shentey@gmail.com, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v4 2/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table
Date: Fri, 4 Mar 2022 11:58:16 +0100 [thread overview]
Message-ID: <20220304115816.45d289a9@redhat.com> (raw)
In-Reply-To: <a9676a57-4ef3-6460-9d8a-8f99e7887047@gmail.com>
On Wed, 2 Mar 2022 17:45:58 +0200
Liav Albani <liavalb@gmail.com> wrote:
> >>> but I feel quoting spec
> >>> and including table name is a good idea actually, but pls quote verbatim:
> >> I don't do that and don't ask it from others.
> >>
> >> The reason being that pointing where to look in spec and having
> >> verbatim copy of field name is sufficient
> >> for looking it up and
> >> QEMU does not endup with half of spec copied in (+unintentional mistakes).
> >> (As reviewer I will check if whatever written in patch actually matches
> >> spec anyways)
> >>
> >> That's why I typically use
> >> 'spec ver, verbatim field name[, chapter/table name]'
> >> policy. The later optional part is usually used for pointing
> >> to values description.
> >
> > Ok but here the field name was not listed verbatim, and table name
> > is missing. It is actually 8042 and table name is Fixed ACPI Description
> > Table Boot Architecture Flags.
> So, in which route should I go with this? I could add a reference to the
> ACPI spec, but can write and explain more if you want me to.
A reference to spec is sufficient, as long as it is unambiguous and lets
a reviewer easily find it within the spec
next prev parent reply other threads:[~2022-03-04 10:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 20:17 [PATCH v4 0/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Liav Albani
2022-02-28 20:17 ` [PATCH v4 1/3] tests/acpi: i386: allow FACP acpi table changes Liav Albani
2022-03-01 2:55 ` Ani Sinha
2022-02-28 20:17 ` [PATCH v4 2/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Liav Albani
2022-03-01 2:59 ` Ani Sinha
2022-03-01 8:48 ` Igor Mammedov
2022-03-01 8:43 ` Igor Mammedov
2022-03-01 9:52 ` Ani Sinha
2022-03-01 11:51 ` Igor Mammedov
2022-03-01 19:20 ` Liav Albani
2022-03-02 5:14 ` Ani Sinha
2022-03-02 12:42 ` Michael S. Tsirkin
2022-03-02 15:43 ` Liav Albani
2022-03-02 15:51 ` Ani Sinha
2022-03-02 15:58 ` Ani Sinha
2022-03-01 11:19 ` Michael S. Tsirkin
2022-03-01 11:47 ` Igor Mammedov
2022-03-01 12:18 ` Michael S. Tsirkin
2022-03-02 15:45 ` Liav Albani
2022-03-04 10:58 ` Igor Mammedov [this message]
2022-03-01 19:11 ` Liav Albani
2022-03-02 5:12 ` Ani Sinha
2022-03-02 8:47 ` Michael S. Tsirkin
2022-02-28 20:17 ` [PATCH v4 3/3] tests/acpi: i386: update FACP table differences Liav Albani
2022-03-01 2:59 ` Ani Sinha
2022-03-01 11:21 ` Michael S. Tsirkin
2022-03-01 19:13 ` Liav Albani
2022-03-02 5:05 ` Ani Sinha
2022-03-02 8:48 ` Michael S. Tsirkin
2022-03-04 10:26 ` [PATCH v4 0/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Michael S. Tsirkin
2022-03-04 10:34 ` Ani Sinha
2022-03-04 10:39 ` Michael S. Tsirkin
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=20220304115816.45d289a9@redhat.com \
--to=imammedo@redhat.com \
--cc=ani@anisinha.ca \
--cc=liavalb@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.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).