From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 00/16] crypto/cipher: Class hierarchy cleanups
Date: Wed, 9 Sep 2020 13:19:41 +0100 [thread overview]
Message-ID: <20200909121941.GQ1011023@redhat.com> (raw)
In-Reply-To: <20200828170523.418603-1-richard.henderson@linaro.org>
On Fri, Aug 28, 2020 at 10:05:07AM -0700, Richard Henderson wrote:
> Mostly this is intended to cleanup the class hierarchy
> used for the ciphers. We currently have multiple levels
> of dispatch, and multiple separate allocations. The final
> patches rearrange this to one level of indirect call, and
> all memory allocated contiguously.
>
> But on the way there are a number of other misc cleanups.
>
> Changes in v2:
> * Dropped move of QCryptoCipher typedef.
> * Moved QCryptoCipherDriver typedef to include/crypto/cipher.h.
> * Renamed included files to *.c.inc.
> * Fixed errors with old versions of nettle and gcrypt.
>
> Based-on: <20200828132716.279782-1-berrange@redhat.com>
> ("crypto: fix build with gcrypt")
>
> which does at least allow *-softmmu builds to complete,
> though I still have issues with *-linux-user.
Thanks, I've queued this series now.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-09-09 12:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 17:05 [PATCH v2 00/16] crypto/cipher: Class hierarchy cleanups Richard Henderson
2020-08-28 17:05 ` [PATCH v2 01/16] crypto: Assume blocksize is a power of 2 Richard Henderson
2020-08-28 17:05 ` [PATCH v2 02/16] crypto: Rename cipher include files to .c.inc Richard Henderson
2020-08-28 17:05 ` [PATCH v2 03/16] crypto: Remove redundant includes Richard Henderson
2020-08-28 17:05 ` [PATCH v2 04/16] crypto/nettle: Fix xts_encrypt arguments Richard Henderson
2020-08-28 17:05 ` [PATCH v2 05/16] crypto: Move QCryptoCipherDriver typedef to crypto/cipher.h Richard Henderson
2020-08-28 17:05 ` [PATCH v2 06/16] crypto: Use the correct const type for driver Richard Henderson
2020-08-28 17:05 ` [PATCH v2 07/16] crypto: Allocate QCryptoCipher with the subclass Richard Henderson
2020-08-28 17:05 ` [PATCH v2 08/16] crypto: Move cipher->driver init to qcrypto_*_cipher_ctx_new Richard Henderson
2020-08-28 17:05 ` [PATCH v2 09/16] crypto: Constify cipher data tables Richard Henderson
2020-08-28 17:05 ` [PATCH v2 10/16] crypto/builtin: Remove odd-sized AES block handling Richard Henderson
2020-08-28 17:05 ` [PATCH v2 11/16] crypto/builtin: Merge qcrypto_cipher_aes_{ecb, xts}_{en, de}crypt Richard Henderson
2020-08-28 17:05 ` [PATCH v2 12/16] crypto/builtin: Move AES_cbc_encrypt into cipher-builtin.inc.c Richard Henderson
2020-08-28 17:05 ` [PATCH v2 13/16] crypto/builtin: Split and simplify AES_encrypt_cbc Richard Henderson
2020-08-28 17:05 ` [PATCH v2 14/16] crypto/builtin: Split QCryptoCipherBuiltin into subclasses Richard Henderson
2020-08-28 17:05 ` [PATCH v2 15/16] crypto/nettle: Split QCryptoCipherNettle " Richard Henderson
2020-08-28 17:05 ` [PATCH v2 16/16] crypto/gcrypt: Split QCryptoCipherGcrypt " Richard Henderson
2020-09-09 12:19 ` Daniel P. Berrangé [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=20200909121941.GQ1011023@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).