DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXTERNAL] [PATCH v4 1/3] common/qat: isolate parser arguments configuration
Date: Thu, 29 Feb 2024 19:19:46 +0000	[thread overview]
Message-ID: <CO6PR18MB448445CE52C272ADE00C71C0D85F2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240229191427.1267-1-arkadiuszx.kusztal@intel.com>

> Subject: [EXTERNAL] [PATCH v4 1/3] common/qat: isolate parser arguments
> configuration
> 
> Prioritize security for external emails: Confirm sender and content safety before
> clicking links or opening attachments
> 
> ----------------------------------------------------------------------
> This commit isolates qat device arguments from the common
> code. Now arguments are defined per service, and only appear
> in the application if the service is compiled-in.
> 
> Depends-on: patch-137466 ("common/qat: add virtual qat device (vQAT)")

Ciara's Gen3/5 series has been merged to next-crypto. 
vQAT series does not apply and hence this would also not apply.
Please rebase and mark dependencies. 
Also mark previous versions as superseded. It creates lot of confusion.
I have been marking your patches as superseded. Please so it while sending the next version.



  parent reply	other threads:[~2024-02-29 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v4-00020240229093007.32298-1-arkadiuszx.kusztal@intel.com>
2024-02-29 19:14 ` Arkadiusz Kusztal
2024-02-29 19:14   ` [PATCH v4 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-02-29 19:14   ` [PATCH v4 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2024-02-29 19:19   ` Akhil Goyal [this message]
2024-03-01 15:52   ` [PATCH v5 1/3] common/qat: isolate parser arguments configuration Arkadiusz Kusztal
2024-03-01 15:52     ` [PATCH v5 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-03-01 16:08       ` Dooley, Brian
2024-03-01 15:52     ` [PATCH v5 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2024-03-01 16:08       ` Dooley, Brian
2024-03-04  7:10         ` Akhil Goyal
2024-03-01 16:07     ` [PATCH v5 1/3] common/qat: isolate parser arguments configuration Dooley, Brian
2024-03-04  7:08     ` [EXTERNAL] " Akhil Goyal

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=CO6PR18MB448445CE52C272ADE00C71C0D85F2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@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).