From: Markus Armbruster <armbru@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 1/1] docs/interop/firmware: Add 'uefi-vars' member for FirmwareMappingMemory
Date: Tue, 17 Feb 2026 16:29:36 +0100 [thread overview]
Message-ID: <87y0krgzhb.fsf@pond.sub.org> (raw)
In-Reply-To: <CABJz62MVB1ThuQ95Y0LVSdJ25mSBrct8FyS7GFhm4PXz_yKqjg@mail.gmail.com> (Andrea Bolognani's message of "Tue, 17 Feb 2026 05:18:59 -0800")
Andrea Bolognani <abologna@redhat.com> writes:
> On Tue, Feb 17, 2026 at 10:08:14AM +0100, Markus Armbruster wrote:
>> > +# @uefi-vars: Information specific to firmware builds that expect the
>> > +# "uefi-vars" device to be used to provide access to the
>> > +# UEFI variable store. If the mapping contains this
>> > +# member, the firmware descriptor should advertise the
>> > +# @uefi interface from @FirmwareOSInterface as well as
>> > +# the @host-uefi-vars feature from @FirmwareFeature.
>> > +# Since 11.0
>> > +#
>>
>> (Since 11.0) and indent like this, please:
>
> Done, but note that the documentation for existing members
> FirmwareDevice::igvm and FirmwareMappingFlash::mode doesn't follow
> this convention.
... where "this convention" is about since. You're right, and I wasn't
aware of it. Thanks!
prev parent reply other threads:[~2026-02-17 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 13:39 [PATCH v2 0/1] docs/interop/firmware: Add 'uefi-vars' member for FirmwareMappingMemory Andrea Bolognani
2026-02-09 13:39 ` [PATCH v2 1/1] " Andrea Bolognani
2026-02-11 16:18 ` Daniel P. Berrangé
2026-02-17 9:08 ` Markus Armbruster
2026-02-17 11:37 ` Gerd Hoffmann
2026-02-17 14:12 ` Andrea Bolognani
2026-02-17 13:18 ` Andrea Bolognani
2026-02-17 15:29 ` Markus Armbruster [this message]
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=87y0krgzhb.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=abologna@redhat.com \
--cc=berrange@redhat.com \
--cc=kchamart@redhat.com \
--cc=kraxel@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--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.