qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Akihiko Odaki <akihiko.odaki@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v5 0/6] crypto: Make QCryptoTLSCreds* structures private
Date: Mon, 28 Jun 2021 15:22:53 +0200	[thread overview]
Message-ID: <5abbc39f-4213-c3e7-8f43-70fea6a2c00e@redhat.com> (raw)
In-Reply-To: <60171e96-dbee-1510-0d09-13ec64b7229f@gmail.com>

On 6/28/21 5:56 AM, Akihiko Odaki wrote:
> Hi,
> 
> qemu-nbd.c still refers to members of QCryptoTLSCreds* and can't be
> compiled.

Thanks for testing, I'll have a look.

> 
> Regards,
> Akihiko Odaki
> 
> On 2021/06/17 21:18, Philippe Mathieu-Daudé wrote:
>> Missing review: 5 & 6
>>
>> Follow Daniel suggestion to simplify qcrypto TLS implementations,
>> aiming to solve the OSX build failure.



      reply	other threads:[~2021-06-28 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 12:18 [PATCH v5 0/6] crypto: Make QCryptoTLSCreds* structures private Philippe Mathieu-Daudé
2021-06-17 12:18 ` [PATCH v5 1/6] crypto/tlscreds: Introduce qcrypto_tls_creds_check_endpoint() helper Philippe Mathieu-Daudé
2021-06-17 12:18 ` [PATCH v5 2/6] block/nbd: Use qcrypto_tls_creds_check_endpoint() Philippe Mathieu-Daudé
2021-06-17 12:18 ` [PATCH v5 3/6] chardev/socket: " Philippe Mathieu-Daudé
2021-06-17 12:18 ` [PATCH v5 4/6] migration/tls: " Philippe Mathieu-Daudé
2021-06-17 12:18 ` [PATCH v5 5/6] ui/vnc: " Philippe Mathieu-Daudé
2021-06-17 15:34   ` Richard Henderson
2021-06-18  8:35   ` Daniel P. Berrangé
2021-06-17 12:18 ` [PATCH v5 6/6] crypto: Make QCryptoTLSCreds* structures private Philippe Mathieu-Daudé
2021-06-18  8:35   ` Daniel P. Berrangé
2021-06-28  3:56 ` [PATCH v5 0/6] " Akihiko Odaki
2021-06-28 13:22   ` Philippe Mathieu-Daudé [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=5abbc39f-4213-c3e7-8f43-70fea6a2c00e@redhat.com \
    --to=philmd@redhat.com \
    --cc=akihiko.odaki@gmail.com \
    --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).