From: Akhil Goyal <gakhil@marvell.com>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>,
Tom Rix <trix@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Zhang, Mingshan" <mingshan.zhang@intel.com>,
"Joshi, Arun" <arun.joshi@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 6/6] bbdev: reduce warning level for one scenario
Date: Tue, 5 Oct 2021 10:05:06 +0000 [thread overview]
Message-ID: <CO6PR18MB4484DB5B4EFCEEB15C8030F0D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <BY5PR11MB4451D216C920F1724A7DA3D6F8AE9@BY5PR11MB4451.namprd11.prod.outlook.com>
> Can this serie below be applied now?
> Thanks and regards,
> Nic
Series Applied to dpd-next-crypto
Thanks.
prev parent reply other threads:[~2021-10-05 10:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 1:15 [dpdk-dev] [PATCH v3 0/6] bbdev update related to CRC usage Nicolas Chautru
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 1/6] bbdev: add capability for CRC16 check Nicolas Chautru
2021-09-12 12:35 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 2/6] baseband/turbo_sw: add support for CRC16 Nicolas Chautru
2021-09-12 12:38 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 3/6] bbdev: add capability for 4G CB CRC DROP Nicolas Chautru
2021-09-12 12:39 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 4/6] baseband/acc100: add support for 4G CRC drop Nicolas Chautru
2021-09-12 12:42 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 5/6] doc: clarification of usage of HARQ in bbdev doc Nicolas Chautru
2021-09-12 12:44 ` Tom Rix
2021-10-11 20:29 ` Thomas Monjalon
2021-10-11 20:33 ` Chautru, Nicolas
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 6/6] bbdev: reduce warning level for one scenario Nicolas Chautru
2021-09-12 12:54 ` Tom Rix
2021-09-13 17:03 ` Chautru, Nicolas
2021-09-13 20:01 ` Tom Rix
2021-10-04 23:40 ` Chautru, Nicolas
2021-10-05 10:05 ` 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=CO6PR18MB4484DB5B4EFCEEB15C8030F0D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arun.joshi@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
--cc=trix@redhat.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).