From: "Daniel P. Berrangé" <berrange@redhat.com>
To: antoine.damhet@shadow.tech
Cc: qemu-devel@nongnu.org, vm@shadow.tech
Subject: Re: [PATCH 1/2] crypto: TLS: introduce `check_pending`
Date: Wed, 16 Nov 2022 10:44:57 +0000 [thread overview]
Message-ID: <Y3S/KQ8SIvGKOOWQ@redhat.com> (raw)
In-Reply-To: <20221115142329.92524-2-antoine.damhet@shadow.tech>
On Tue, Nov 15, 2022 at 03:23:28PM +0100, antoine.damhet@shadow.tech wrote:
> From: Antoine Damhet <antoine.damhet@shadow.tech>
>
> The new `qcrypto_tls_session_check_pending` function allows the caller
> to know if data have already been consumed from the backend and is
> already available.
>
> Signed-off-by: Antoine Damhet <antoine.damhet@shadow.tech>
> ---
> crypto/tlssession.c | 14 ++++++++++++++
> include/crypto/tlssession.h | 11 +++++++++++
> 2 files changed, 25 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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 :|
next prev parent reply other threads:[~2022-11-16 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 14:23 [PATCH 0/2] TLS: fix read stall with large buffers antoine.damhet
2022-11-15 14:23 ` [PATCH 1/2] crypto: TLS: introduce `check_pending` antoine.damhet
2022-11-16 10:44 ` Daniel P. Berrangé [this message]
2022-11-15 14:23 ` [PATCH 2/2] io/channel-tls: fix handling of bigger read buffers antoine.damhet
2022-11-16 10:52 ` Daniel P. Berrangé
2022-12-16 10:38 ` Antoine Damhet
2022-12-16 10:55 ` Daniel P. Berrangé
2024-02-28 16:11 ` Thomas Huth
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=Y3S/KQ8SIvGKOOWQ@redhat.com \
--to=berrange@redhat.com \
--cc=antoine.damhet@shadow.tech \
--cc=qemu-devel@nongnu.org \
--cc=vm@shadow.tech \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.