From: "Power, Ciara" <ciara.power@intel.com>
To: "Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
"Ji, Kai" <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH v1] common/qat: fix qat_dev_cmd_param corruption
Date: Thu, 8 Jun 2023 13:08:51 +0000 [thread overview]
Message-ID: <SN7PR11MB763996F4A9D8C3B49F7077D3E650A@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230523090641.1659274-1-vikash.chandrax.poddar@intel.com>
> -----Original Message-----
> From: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> Sent: Tuesday 23 May 2023 10:07
> To: Ji, Kai <kai.ji@intel.com>
> Cc: dev@dpdk.org; Poddar, Vikash ChandraX
> <vikash.chandrax.poddar@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v1] common/qat: fix qat_dev_cmd_param corruption
>
> Adding fix to address the memory corruption issue for qat_dev_cmd_param
> structure on QAT GEN3.
>
> This fix aligns the storage where it stores the value on 4 byte unsigned
> integer data type after reading slice configuration of QAT capabilities.
>
> Fixes: b3cbbcdffa4f ("common/qat: read HW slice configuration")
> Cc: arkadiuszx.kusztal@intel.com
>
> Signed-off-by: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> ---
<snip>
Acked-by: Ciara Power <ciara.power@intel.com>
prev parent reply other threads:[~2023-06-08 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 9:06 Vikash Poddar
2023-05-25 15:38 ` [PATCH v2] " Vikash Poddar
2023-06-16 14:50 ` Poddar, Vikash ChandraX
2023-06-08 13:08 ` Power, Ciara [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=SN7PR11MB763996F4A9D8C3B49F7077D3E650A@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--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).