From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] crypto/cipher-nettle.c: Pass correct function type to cbc_encrypt and cbc_decrypt.
Date: Thu, 16 Jul 2015 12:08:49 +0200 [thread overview]
Message-ID: <55A782B1.9080209@redhat.com> (raw)
In-Reply-To: <CAFEAcA94tTxDphiNk1YzjxGR2fOV0uzL4CwnureRM-usnWXcxg@mail.gmail.com>
On 16/07/2015 12:04, Peter Maydell wrote:
> Is this the same issue that Radim's patchset from a few days
> back is addressing?
Yes. Are you going to apply it, or should I include it in the pull
request I'll send out today?
Paolo
next prev parent reply other threads:[~2015-07-16 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 9:55 [Qemu-devel] [PATCH] crypto/cipher-nettle.c: Pass correct function type to cbc_encrypt and cbc_decrypt Richard W.M. Jones
2015-07-16 10:04 ` Peter Maydell
2015-07-16 10:08 ` Paolo Bonzini [this message]
2015-07-16 10:12 ` Peter Maydell
2015-07-16 10:28 ` Richard W.M. Jones
2015-07-17 10:47 ` Daniel P. Berrange
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=55A782B1.9080209@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).