From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Chen Qun <kuhn.chenqun@huawei.com>
Cc: qemu-trivial@nongnu.org, zhang.zhanghailiang@huawei.com,
Euler Robot <euler.robot@huawei.com>,
qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: [PATCH v2] crypto: Redundant type conversion for AES_KEY pointer
Date: Tue, 5 May 2020 10:15:33 +0100 [thread overview]
Message-ID: <20200505091533.GD764268@redhat.com> (raw)
In-Reply-To: <20200505085940.28592-1-kuhn.chenqun@huawei.com>
On Tue, May 05, 2020 at 04:59:40PM +0800, Chen Qun wrote:
> We can delete the redundant type conversion if
> we set the the AES_KEY parameter with 'const' in
> qcrypto_cipher_aes_ecb_(en|de)crypt() function.
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Chen Qun <kuhn.chenqun@huawei.com>
> ---
> v1->v2:
> Cc: "Daniel P. Berrangé" <berrange@redhat.com>
>
> Modify the AES_KEY parameter with 'const' in
> qcrypto_cipher_aes_ecb_(en|de)crypt() methods.
> (Base on Daniel P. Berrangé's suggestion)
>
> https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg00515.html
>
> ---
> crypto/cipher-builtin.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
and queued - will send a PR with this and some other crypto fixes later
today most likely.
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-05-05 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 8:59 [PATCH v2] crypto: Redundant type conversion for AES_KEY pointer Chen Qun
2020-05-05 9:15 ` 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=20200505091533.GD764268@redhat.com \
--to=berrange@redhat.com \
--cc=euler.robot@huawei.com \
--cc=kuhn.chenqun@huawei.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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).