From: Martin KaFai Lau <martin.lau@linux.dev>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
bpf@vger.kernel.org, Victor Stewart <v@nametag.social>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH bpf-next v8 1/3] bpf: make common crypto API for TC/XDP programs
Date: Tue, 23 Jan 2024 16:12:50 -0800 [thread overview]
Message-ID: <3a0dc098-9b21-4f0b-96a4-de2f55bc8147@linux.dev> (raw)
In-Reply-To: <52e5df2c-1faf-479f-8b64-a5d0c86c82e5@linux.dev>
On 1/23/24 9:51 AM, Vadim Fedorenko wrote:
> gentle ping here? it's more than a week with no feedback...
It is in my list. I have some backlog. will try to get to it tomorrow.
next prev parent reply other threads:[~2024-01-24 0:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 22:08 [PATCH bpf-next v8 1/3] bpf: make common crypto API for TC/XDP programs Vadim Fedorenko
2024-01-15 22:08 ` [PATCH bpf-next v8 2/3] bpf: crypto: add skcipher to bpf crypto Vadim Fedorenko
2024-01-25 1:14 ` Martin KaFai Lau
2024-01-25 9:24 ` Herbert Xu
2024-01-15 22:08 ` [PATCH bpf-next v8 3/3] selftests: bpf: crypto skcipher algo selftests Vadim Fedorenko
2024-01-25 1:26 ` Martin KaFai Lau
2024-02-21 8:43 ` Jakub Sitnicki
2024-02-21 9:19 ` Jakub Sitnicki
2024-01-23 17:51 ` [PATCH bpf-next v8 1/3] bpf: make common crypto API for TC/XDP programs Vadim Fedorenko
2024-01-24 0:12 ` Martin KaFai Lau [this message]
2024-01-25 1:10 ` Martin KaFai Lau
2024-01-25 11:19 ` Vadim Fedorenko
2024-01-25 22:34 ` Martin KaFai Lau
2024-01-26 10:30 ` Vadim Fedorenko
2024-01-26 17:38 ` Vadim Fedorenko
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=3a0dc098-9b21-4f0b-96a4-de2f55bc8147@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=v@nametag.social \
--cc=vadim.fedorenko@linux.dev \
/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.