qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, alejandro.zeise@seagate.com,
	peter.maydell@linaro.org
Subject: Re: [PATCH] crypto/hash-afalg: Fix broken build
Date: Thu, 17 Oct 2024 09:11:50 +0100	[thread overview]
Message-ID: <ZxDDHPl1vhoNyVvV@redhat.com> (raw)
In-Reply-To: <0a727cfe-af7c-4838-9336-2a6b2b555b8e@redhat.com>

On Thu, Oct 17, 2024 at 08:54:04AM +0200, Cédric Le Goater wrote:
> On 10/17/24 08:47, Markus Armbruster wrote:
> > Fux build broken by semantic conflict with commit
> > 8f525028bc6 (qapi/crypto: Rename QCryptoAFAlg to QCryptoAFAlgo).
> > 
> > Fixes: 90c3dc60735a (crypto/hash-afalg: Implement new hash API)
> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
> 
> My bad :/ Obviously, I didn't catch this at compile time, nor did CI.

Yeah, this is a clear gap in our CI that I will post a patch for.

> Reviewed-by: Cédric Le Goater <clg@redhat.com>

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

> 
> Thanks,
> 
> C.
> 
> 
> > ---
> >   crypto/hash-afalg.c | 10 +++++-----
> >   1 file changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/crypto/hash-afalg.c b/crypto/hash-afalg.c
> > index 06e1e4699c..8c0ce5b520 100644
> > --- a/crypto/hash-afalg.c
> > +++ b/crypto/hash-afalg.c
> > @@ -142,7 +142,7 @@ QCryptoHash *qcrypto_afalg_hash_new(QCryptoHashAlgo alg, Error **errp)
> >   static
> >   void qcrypto_afalg_hash_free(QCryptoHash *hash)
> >   {
> > -    QCryptoAFAlg *ctx = hash->opaque;
> > +    QCryptoAFAlgo *ctx = hash->opaque;
> >       if (ctx) {
> >           qcrypto_afalg_comm_free(ctx);
> > @@ -159,7 +159,7 @@ void qcrypto_afalg_hash_free(QCryptoHash *hash)
> >    * be provided to calculate the final hash.
> >    */
> >   static
> > -int qcrypto_afalg_send_to_kernel(QCryptoAFAlg *afalg,
> > +int qcrypto_afalg_send_to_kernel(QCryptoAFAlgo *afalg,
> >                                    const struct iovec *iov,
> >                                    size_t niov,
> >                                    bool more_data,
> > @@ -183,7 +183,7 @@ int qcrypto_afalg_send_to_kernel(QCryptoAFAlg *afalg,
> >   }
> >   static
> > -int qcrypto_afalg_recv_from_kernel(QCryptoAFAlg *afalg,
> > +int qcrypto_afalg_recv_from_kernel(QCryptoAFAlgo *afalg,
> >                                      QCryptoHashAlgo alg,
> >                                      uint8_t **result,
> >                                      size_t *result_len,
> > @@ -222,7 +222,7 @@ int qcrypto_afalg_hash_update(QCryptoHash *hash,
> >                                 size_t niov,
> >                                 Error **errp)
> >   {
> > -    return qcrypto_afalg_send_to_kernel((QCryptoAFAlg *) hash->opaque,
> > +    return qcrypto_afalg_send_to_kernel((QCryptoAFAlgo *) hash->opaque,
> >                                           iov, niov, true, errp);
> >   }
> > @@ -232,7 +232,7 @@ int qcrypto_afalg_hash_finalize(QCryptoHash *hash,
> >                                    size_t *result_len,
> >                                    Error **errp)
> >   {
> > -    return qcrypto_afalg_recv_from_kernel((QCryptoAFAlg *) hash->opaque,
> > +    return qcrypto_afalg_recv_from_kernel((QCryptoAFAlgo *) hash->opaque,
> >                                             hash->alg, result, result_len, errp);
> >   }
> 
> 

With 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 :|



      parent reply	other threads:[~2024-10-17  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  6:47 [PATCH] crypto/hash-afalg: Fix broken build Markus Armbruster
2024-10-17  6:54 ` Cédric Le Goater
2024-10-17  7:58   ` Markus Armbruster
2024-10-17  8:11   ` 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=ZxDDHPl1vhoNyVvV@redhat.com \
    --to=berrange@redhat.com \
    --cc=alejandro.zeise@seagate.com \
    --cc=armbru@redhat.com \
    --cc=clg@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).