DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Brian Dooley <brian.dooley@intel.com>
Cc: Kai Ji <kai.ji@intel.com>,
	dev@dpdk.org, stable@dpdk.org, gakhil@marvell.com
Subject: Re: [PATCH v2] doc: update QAT device support
Date: Tue, 22 Nov 2022 10:17:05 +0100	[thread overview]
Message-ID: <3522595.R56niFO833@thomas> (raw)
In-Reply-To: <20221118171909.134666-1-brian.dooley@intel.com>

18/11/2022 18:19, Brian Dooley:
> Update what drivers and devices are supported for Asymmetric Crypto
> Service on QAT
> 
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
Acked-by: Kai Ji <kai.ji@intel.com>

Applied, thanks.



      parent reply	other threads:[~2022-11-22  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 14:34 [PATCH v1] " Brian Dooley
2022-11-18 17:19 ` [PATCH v2] " Brian Dooley
2022-11-21 16:12   ` Ji, Kai
2022-11-22  9:17   ` Thomas Monjalon [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=3522595.R56niFO833@thomas \
    --to=thomas@monjalon.net \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=stable@dpdk.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).