From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Kashyap Chamarthy <kchamart@redhat.com>,
libvirt devel <libvir-list@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
David Gibson <dgibson@redhat.com>
Subject: Re: [Qemu-devel] [qemu PATCH v2] docs/interop: add "firmware.json"
Date: Thu, 24 May 2018 19:28:17 +0200 [thread overview]
Message-ID: <e6e44c18-c23b-35a1-cc07-8ddf37f6d6c3@redhat.com> (raw)
In-Reply-To: <1835b91a-57ab-eb7e-dd98-68421c19a425@redhat.com>
On 05/24/18 18:23, Paolo Bonzini wrote:
> On 24/05/2018 18:21, Laszlo Ersek wrote:
>> On 05/15/18 11:49, Gerd Hoffmann wrote:
>>> On Wed, May 09, 2018 at 05:26:08PM +0200, Laszlo Ersek wrote:
>>>> Add a schema that describes the different uses and properties of virtual
>>>> machine firmware.
>>>>
>>>> Each firmware executable installed on a host system should come with at
>>>> least one JSON file that conforms to this schema. Each file informs the
>>>> management applications about
>>>> - the firmware's properties and one possible use case / feature set,
>>>> - configuration bits that are required to run the firmware binary.
>>>>
>>>> In addition, define rules for management apps for picking the highest
>>>> priority firmware JSON file when multiple such files match the search
>>>> criteria.
>>>
>>> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>>
>> Thanks, Gerd!
>>
>> Does anyone else intend to comment? Or should I ask for someone to queue
>> the patch for a pull request?
>
> Since no one has done that so far I've queued it, thanks!
Awesome; huge kudos!
Laszlo
prev parent reply other threads:[~2018-05-24 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:26 [Qemu-devel] [qemu PATCH v2] docs/interop: add "firmware.json" Laszlo Ersek
2018-05-15 9:49 ` Gerd Hoffmann
2018-05-24 16:21 ` Laszlo Ersek
2018-05-24 16:23 ` Paolo Bonzini
2018-05-24 17:28 ` Laszlo Ersek [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=e6e44c18-c23b-35a1-cc07-8ddf37f6d6c3@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=dgibson@redhat.com \
--cc=kchamart@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--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).