From: Patrick Robb <probb@iol.unh.edu>
To: Brian Dooley <brian.dooley@intel.com>
Cc: Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
dev@dpdk.org, gakhil@marvell.com
Subject: Re: [PATCH v1] crypto/ipsec_mb: use new ipad/opad calculation API
Date: Tue, 2 Jul 2024 09:32:09 -0400 [thread overview]
Message-ID: <CAJvnSUAGtOZ_Oy95PdDYtNscRgRpts-_e5kBh7q6=hdky60n_w@mail.gmail.com> (raw)
In-Reply-To: <20240605084844.270122-1-brian.dooley@intel.com>
Recheck-request: iol-unit-arm64-testing
next prev parent reply other threads:[~2024-07-02 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:48 Brian Dooley
2024-06-10 8:19 ` Dooley, Brian
2024-06-20 9:00 ` Dooley, Brian
2024-06-24 14:33 ` Ji, Kai
2024-06-27 14:35 ` Wathsala Wathawana Vithanage
2024-07-03 17:26 ` Akhil Goyal
2024-07-02 13:32 ` Patrick Robb [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-14 16:41 Brian Dooley
2024-02-08 16:15 ` Power, Ciara
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='CAJvnSUAGtOZ_Oy95PdDYtNscRgRpts-_e5kBh7q6=hdky60n_w@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
/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).