From: Peter Maydell <peter.maydell@linaro.org>
To: NaNa Liu <nanliu@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, kraxel@redhat.com,
"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>
Subject: Re: [PATCH] docs/devel: Correct uefi-vars-x64 device name
Date: Thu, 30 Oct 2025 10:34:24 +0000 [thread overview]
Message-ID: <CAFEAcA8mC-VbD-29=7XLMiEQ0yhdKAaHzxWyKt5NXmUsjHgmBA@mail.gmail.com> (raw)
In-Reply-To: <CANUVZAznv1aP5DH6pHEQBZGxczkoNVQfKR5oOV7eTyrk4rVrpQ@mail.gmail.com>
On Thu, 30 Oct 2025 at 05:47, NaNa Liu <nanliu@redhat.com> wrote:
>
>
>
> On Sat, Sep 27, 2025 at 7:41 PM Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Sat, 27 Sept 2025 at 09:48, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> >
>> > On 23.09.2025 14:57, Peter Maydell wrote:
>> >
>> > > We could probably also correct the bit of the text in this file
>> > > that currently reads "depend on SMM emulation on x64" to either
>> > > say "x86" or "x86_64".
>> >
>> > This one will be a bit more than trivial :) I for one don't know
>> > if this is related to any x86 or to x86_64 only.
>>
>> I just mean exactly and specifically the one place in this
>> file which says "x64" and ought to say either "x86" or
>> "x86_64". To me a single word change is pretty trivial,
>> especially since nowhere else in our docs do we use "x64".
>>
> This is to ensure consistency between the documentation and the API code (var-service-api.h) parameters and json file, which use "uefi-vars-x64".
The device name being "uefi-vars-x64" is unfortunate, but we
can't change that. We should be consistent about how we talk
about the architecture name in general when our hands are not
tied by compatibility problems.
-- PMM
next prev parent reply other threads:[~2025-10-30 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 6:57 [PATCH] docs/devel: Correct uefi-vars-x64 device name nanliu
2025-09-22 7:38 ` Thomas Huth
2025-09-23 11:57 ` Peter Maydell
2025-09-27 8:48 ` Michael Tokarev
2025-09-27 11:41 ` Peter Maydell
2025-10-30 5:46 ` NaNa Liu
2025-10-30 10:34 ` Peter Maydell [this message]
2025-10-30 12:56 ` Gerd Hoffmann
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='CAFEAcA8mC-VbD-29=7XLMiEQ0yhdKAaHzxWyKt5NXmUsjHgmBA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=nanliu@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).