From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: "Gabriel L. Somlo" <somlo@cmu.edu>,
Laszlo Ersek <lersek@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.6] fw_cfg: Adopt /opt/RFQDN convention
Date: Mon, 18 Apr 2016 12:58:18 -0600 [thread overview]
Message-ID: <57152E4A.30907@redhat.com> (raw)
In-Reply-To: <1460997729-29541-1-git-send-email-armbru@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On 04/18/2016 10:42 AM, Markus Armbruster wrote:
> FW CFG's primary user is QEMU, which uses it to expose configuration
> information (in the widest sense) to Firmware. Thus the name FW CFG.
>
> FW CFG can also be used by others for their own purposes. QEMU is
> merely acting as transport then. Names starting with opt/ are reseved
s/reseved/reserved/
> for such uses. There is no provision, however, to guide safe sharing
> among different such users.
>
> Fix that, losely following QMP precedence: names should start with
s/losely/loosely/
> opt/RFQDN/, where RFQDN is a reverse fully qualified domain name you
> control.
>
> Based on a more ambitious patch from Michael Tsirkin.
>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Gabriel L. Somlo <somlo@cmu.edu>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-04-18 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 16:42 [Qemu-devel] [PATCH for-2.6] fw_cfg: Adopt /opt/RFQDN convention Markus Armbruster
2016-04-18 16:49 ` Michael S. Tsirkin
2016-04-19 7:48 ` Markus Armbruster
2016-04-19 13:04 ` Gabriel L. Somlo
2016-04-18 18:58 ` Eric Blake [this message]
2016-04-19 8:30 ` Markus Armbruster
2016-04-19 13:08 ` Laszlo Ersek
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=57152E4A.30907@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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).