From: "Radim Krčmář" <rkrcmar@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2 2/3] crypto: avoid undefined behavior in nettle calls
Date: Sat, 11 Jul 2015 11:52:40 +0200 [thread overview]
Message-ID: <20150711095239.GA12149@potion.redhat.com> (raw)
In-Reply-To: <1436548682-9315-3-git-send-email-rkrcmar@redhat.com>
2015-07-10 19:18+0200, Radim Krčmář:
> diff --git a/crypto/cipher-nettle.c b/crypto/cipher-nettle.c
> +void aes_encrypt_wrapper(cipher_ctx_t ctx, cipher_length_t length,
> + uint8_t *dst, const uint8_t *src)
Wrappers should be static (rushed posting). I'll send v3 on Wed/Thu.
> +{
> + aes_encrypt(ctx, length, dst, src);
> +}
next prev parent reply other threads:[~2015-07-11 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 17:17 [Qemu-devel] [PATCH v2 0/3] crypto: nettle fixes Radim Krčmář
2015-07-10 17:18 ` [Qemu-devel] [PATCH v2 1/3] crypto: fix build with nettle >= 3.0.0 Radim Krčmář
2015-07-10 17:18 ` [Qemu-devel] [PATCH v2 2/3] crypto: avoid undefined behavior in nettle calls Radim Krčmář
2015-07-11 9:52 ` Radim Krčmář [this message]
2015-07-10 17:18 ` [Qemu-devel] [PATCH v2 3/3] crypto: use CPP for wrapper definitions in nettle Radim Krčmář
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=20150711095239.GA12149@potion.redhat.com \
--to=rkrcmar@redhat.com \
--cc=peter.maydell@linaro.org \
--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).