From: Akhil Goyal <gakhil@marvell.com>
To: Brian Dooley <brian.dooley@intel.com>, Kai Ji <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>
Subject: RE: [EXT] [PATCH v2] doc: update QAT kernel module entry
Date: Mon, 23 Oct 2023 13:50:34 +0000 [thread overview]
Message-ID: <CO6PR18MB44846DE80E7BCF933BD9747CD8D8A@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20231013130656.900115-1-brian.dooley@intel.com>
> The Kernel Module entry for 2.0 devices was incorrect in the doc table.
> Updated table with Kernel Module qat_4xxx.
>
> Fixes: f4eac3a09c51 ("common/qat: enable GEN4 b devices")
> Cc: arkadiuszx.kusztal@intel.com
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-10-23 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:59 [PATCH v1] " Brian Dooley
2023-10-13 11:27 ` David Marchand
2023-10-13 13:06 ` [PATCH v2] " Brian Dooley
2023-10-23 13:50 ` Akhil Goyal [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=CO6PR18MB44846DE80E7BCF933BD9747CD8D8A@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@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).