patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
	"Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
	"Ji, Kai" <kai.ji@intel.com>, Fan Zhang <fanzhang.oss@gmail.com>,
	Ashish Gupta <ashishg@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v3] common/qat: fix detach QAT crypto compress build
Date: Mon, 3 Jul 2023 14:26:31 +0000	[thread overview]
Message-ID: <CO6PR18MB44841E3DEB34A0426644D186D829A@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN7PR11MB763958E65FFD6D33B68D6222E624A@SN7PR11MB7639.namprd11.prod.outlook.com>

> > Subject: [PATCH v3] common/qat: fix detach QAT crypto compress build
> >
> > qat_qp.c is a common file for QAT crypto and compress. Moved compress
> > function from common file to compress QAT file qat_comp.c
> >
> > Bugzilla ID: 1237
> > Fixes: 2ca75c65af4c ("common/qat: build drivers from common folder")
> > Cc: bruce.richardson@intel.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> > ---
> > v3:
> > Fixed commit message
> > v2:
> > Fixed coding style issue
> 
> Acked-by: Ciara Power <ciara.power@intel.com>
Applied to dpdk-next-crypto
Thanks.

      reply	other threads:[~2023-07-03 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 13:48 [PATCH v1] common/qat: " Vikash Poddar
2023-06-23 14:47 ` [PATCH v2] " Vikash Poddar
2023-06-26 11:29   ` [PATCH v3] common/qat: fix " Vikash Poddar
2023-06-28  9:10     ` Power, Ciara
2023-07-03 14:26       ` 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=CO6PR18MB44841E3DEB34A0426644D186D829A@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ashishg@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=kai.ji@intel.com \
    --cc=stable@dpdk.org \
    --cc=vikash.chandrax.poddar@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).