From: Gerd Hoffmann <kraxel@redhat.com>
To: Lei Li <lilei@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix the inconsistency in x509-dh-key-file parameter
Date: Mon, 19 Nov 2012 10:59:52 +0100 [thread overview]
Message-ID: <50AA0318.8010003@redhat.com> (raw)
In-Reply-To: <1353316508-16816-1-git-send-email-lilei@linux.vnet.ibm.com>
On 11/19/12 10:15, Lei Li wrote:
> Commit c448e8552b0f6135dabddf944a7110f929c08320 (spice: tls
> support) added options to the -spice command line. But there
> is an inconsistency between the declaration of the option
> 'x509-dh-key-file' to -spice command line and its parameter
> parsing 'x509-dh-file' in function qemu_spice_init.
Patch added to spice patch queue.
thanks,
Gerd
next prev parent reply other threads:[~2012-11-19 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 9:15 [Qemu-devel] [PATCH] Fix the inconsistency in x509-dh-key-file parameter Lei Li
2012-11-19 9:59 ` Gerd Hoffmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-15 7:09 Lei Li
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=50AA0318.8010003@redhat.com \
--to=kraxel@redhat.com \
--cc=lilei@linux.vnet.ibm.com \
--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 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).