From: Nipun Gupta <nipun.gupta@nxp.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"trix@redhat.com" <trix@redhat.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"mingshan.zhang@intel.com" <mingshan.zhang@intel.com>,
"arun.joshi@intel.com" <arun.joshi@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v9] bbdev: add device info related to data endianness assumption
Date: Thu, 7 Oct 2021 02:22:10 +0000 [thread overview]
Message-ID: <DB9PR04MB84290E9EF93E5086EF41A2F6E6B19@DB9PR04MB8429.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1633553929-58670-1-git-send-email-nicolas.chautru@intel.com>
Sure Nicolas, this seems fine.
I'll use this change instead of existing patch 1/10 and send a re-spin.
Thanks,
Nipun
> -----Original Message-----
> From: Nicolas Chautru <nicolas.chautru@intel.com>
> Sent: Thursday, October 7, 2021 2:29 AM
> To: dev@dpdk.org; gakhil@marvell.com; Nipun Gupta <nipun.gupta@nxp.com>;
> trix@redhat.com
> Cc: thomas@monjalon.net; mingshan.zhang@intel.com; arun.joshi@intel.com;
> Hemant Agrawal <hemant.agrawal@nxp.com>; david.marchand@redhat.com;
> Nicolas Chautru <nicolas.chautru@intel.com>
> Subject: [PATCH v9] bbdev: add device info related to data endianness
> assumption
>
> Suggesting this bbdev api change attached to address the requirement for the
> new
> bbdev PMD from this serie :
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatches.
> dpdk.org%2Fproject%2Fdpdk%2Fpatch%2F20211006113112.11163-2-
> nipun.gupta%40nxp.com%2F&data=04%7C01%7Cnipun.gupta%40nxp.com
> %7Cd99e521071fc4162dfa508d9890c1b8a%7C686ea1d3bc2b4c6fa92cd99c5c30
> 1635%7C0%7C0%7C637691507373998592%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
> 1000&sdata=ogEvbxTKLnCAPs1cuIN76bXb1Mjty0crd3wotOmw%2Fcg%3D
> &reserved=0
> Nipin, please review and you can use this one in case that is okay with you.
> This is defined as an enum and default values set in existing PMDs.
>
> Nicolas Chautru (1):
> bbdev: add device info related to data endianness assumption
>
> doc/guides/rel_notes/release_21_11.rst | 1 +
> drivers/baseband/acc100/rte_acc100_pmd.c | 1 +
> drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 1 +
> drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 1 +
> drivers/baseband/turbo_sw/bbdev_turbo_software.c | 1 +
> lib/bbdev/rte_bbdev.h | 8 ++++++++
> 6 files changed, 13 insertions(+)
>
> --
> 1.8.3.1
prev parent reply other threads:[~2021-10-07 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 20:58 Nicolas Chautru
2021-10-06 20:58 ` Nicolas Chautru
2021-10-07 12:01 ` Tom Rix
2021-10-07 15:19 ` Chautru, Nicolas
2021-10-07 13:13 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-07 15:41 ` Chautru, Nicolas
2021-10-07 16:49 ` Nipun Gupta
2021-10-07 18:58 ` Chautru, Nicolas
2021-10-08 4:34 ` Nipun Gupta
2021-10-07 2:22 ` Nipun Gupta [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=DB9PR04MB84290E9EF93E5086EF41A2F6E6B19@DB9PR04MB8429.eurprd04.prod.outlook.com \
--to=nipun.gupta@nxp.com \
--cc=arun.joshi@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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).