From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Adel Abouchaev <adel.abushaev@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, corbet@lwn.net, dsahern@kernel.org,
shuah@kernel.org, paul@paul-moore.com, jmorris@namei.org,
serge@hallyn.com, linux-security-module@vger.kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>
Subject: Re: [net-next v4 1/6] net: Documentation on QUIC kernel Tx crypto.
Date: Fri, 9 Sep 2022 08:40:17 +0700 [thread overview]
Message-ID: <d9c17e2a-48f4-e7fd-7cbb-c47e7cffcd72@gmail.com> (raw)
In-Reply-To: <20220909001238.3965798-2-adel.abushaev@gmail.com>
On 9/9/22 07:12, Adel Abouchaev wrote:
> Add documentation for kernel QUIC code.
>
LGTM, thanks.
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-09-09 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Adel Abouchaev <adel.abushaev@gmail.com>
2022-09-09 0:12 ` [net-next v4 0/6] net: support QUIC crypto Adel Abouchaev
2022-09-09 0:12 ` [net-next v4 1/6] net: Documentation on QUIC kernel Tx crypto Adel Abouchaev
2022-09-09 1:40 ` Bagas Sanjaya [this message]
2022-09-09 0:12 ` [net-next v4 2/6] net: Define QUIC specific constants, control and data plane structures Adel Abouchaev
2022-09-09 0:12 ` [net-next v4 3/6] net: Add UDP ULP operations, initialization and handling prototype functions Adel Abouchaev
2022-09-09 0:12 ` [net-next v4 4/6] net: Implement QUIC offload functions Adel Abouchaev
2022-09-09 0:12 ` [net-next v4 5/6] net: Add flow counters and Tx processing error counter Adel Abouchaev
2022-09-09 0:12 ` [net-next v4 6/6] net: Add self tests for ULP operations, flow setup and crypto tests Adel Abouchaev
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=d9c17e2a-48f4-e7fd-7cbb-c47e7cffcd72@gmail.com \
--to=bagasdotme@gmail.com \
--cc=adel.abushaev@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=shuah@kernel.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).