From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] common/qat: fix vf2pf answer
Date: Sun, 28 Aug 2022 09:29:28 +0000 [thread overview]
Message-ID: <CO6PR18MB4484F0B7576AF852F154A0D6D8779@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB580977BC036968A9FB9590DAB8629@MW5PR11MB5809.namprd11.prod.outlook.com>
> > Subject: [PATCH] common/qat: fix vf2pf answer
> >
> > This commit fixes answer sent to physical device in
> > vf2pf communication.
> >
> > Fixes: b17d16fb47b4 ("common/qat: add PF to VF communication")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2022-08-28 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 7:47 Arek Kusztal
2022-08-09 9:34 ` Zhang, Roy Fan
2022-08-28 9:29 ` 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=CO6PR18MB4484F0B7576AF852F154A0D6D8779@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).