From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Shijith Thotton <sthotton@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "pbhagavatula@marvell.com" <pbhagavatula@marvell.com>
Subject: Re: [dpdk-stable] [PATCH 20.11 0/3] backport of octeontx2 patches
Date: Thu, 17 Jun 2021 02:54:07 +0000 [thread overview]
Message-ID: <DM4PR12MB5373D3E2888FBDA34966C5B2A10E9@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <cover.1623868710.git.sthotton@marvell.com>
Hi Shijith,
Thanks for providing the backport series, applied.
Xueming
> -----Original Message-----
> From: Shijith Thotton <sthotton@marvell.com>
> Sent: Thursday, June 17, 2021 2:42 AM
> To: stable@dpdk.org
> Cc: Shijith Thotton <sthotton@marvell.com>; Xueming(Steven) Li <xuemingl@nvidia.com>; pbhagavatula@marvell.com
> Subject: [PATCH 20.11 0/3] backport of octeontx2 patches
>
> Backported below octeontx2 patches for 20.11.
>
> Pavan Nikhilesh (1):
> event/octeontx2: fix XAQ pool reconfigure
>
> Shijith Thotton (2):
> event/octeontx2: fix crypto adapter queue pair operations
> event/octeontx2: configure crypto adapter xaq pool
>
> drivers/common/octeontx2/otx2_mbox.h | 7 ++
> drivers/crypto/octeontx2/otx2_cryptodev_qp.h | 4 +-
> drivers/event/octeontx2/otx2_evdev.c | 31 ++++-
> drivers/event/octeontx2/otx2_evdev_adptr.c | 2 +-
> .../event/octeontx2/otx2_evdev_crypto_adptr.c | 110 +++++++++++++-----
> 5 files changed, 116 insertions(+), 38 deletions(-)
>
> --
> 2.25.1
prev parent reply other threads:[~2021-06-17 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 18:42 Shijith Thotton
2021-06-16 18:42 ` [dpdk-stable] [PATCH 20.11 1/3] event/octeontx2: fix crypto adapter queue pair operations Shijith Thotton
2021-06-16 18:42 ` [dpdk-stable] [PATCH 20.11 2/3] event/octeontx2: configure crypto adapter xaq pool Shijith Thotton
2021-06-16 18:42 ` [dpdk-stable] [PATCH 20.11 3/3] event/octeontx2: fix XAQ pool reconfigure Shijith Thotton
2021-06-17 2:54 ` Xueming(Steven) Li [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=DM4PR12MB5373D3E2888FBDA34966C5B2A10E9@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
--cc=sthotton@marvell.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).