From: Gerd Hoffmann <kraxel@redhat.com>
To: "Gabriel L. Somlo" <somlo@cmu.edu>
Cc: pbonzini@redhat.com, lersek@redhat.com, qemu-devel@nongnu.org,
jordan.l.justen@intel.com
Subject: Re: [Qemu-devel] [PATCH v2] fw_cfg: insert string blobs via qemu cmdline
Date: Tue, 29 Sep 2015 10:51:46 +0200 [thread overview]
Message-ID: <1443516706.21557.16.camel@redhat.com> (raw)
In-Reply-To: <1443455989-3410-1-git-send-email-somlo@cmu.edu>
Hi,
> +Small enough items may be provided directly as strings on the command
> +line, using the syntax:
> +
> + -fw_cfg [name=]<item_name>,content=<string>
Make that "string=<string>"? So things are more clear in case we add a
"int64=<value>" some day?
cheers,
Gerd
prev parent reply other threads:[~2015-09-29 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 15:59 [Qemu-devel] [PATCH v2] fw_cfg: insert string blobs via qemu cmdline Gabriel L. Somlo
2015-09-28 16:28 ` Laszlo Ersek
2015-09-29 8:51 ` Gerd Hoffmann [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=1443516706.21557.16.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=jordan.l.justen@intel.com \
--cc=lersek@redhat.com \
--cc=pbonzini@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).