DPDK patches and discussions
 help / color / mirror / Atom feed
From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, ranish@nvidia.com, ferruh.yigit@intel.com,
	bingz@nvidia.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH] ethdev: fix eCPRI header generic data field
Date: Mon, 23 Nov 2020 12:29:41 +0000	[thread overview]
Message-ID: <1606134581-10742-1-git-send-email-viacheslavo@nvidia.com> (raw)

There was a typo in eCPRI header definition.

Fixes: d164c609e70b ("ethdev: add eCPRI key fields to flow API")
Cc: stable@dpdk.org

Reported-by: Rani Sharoni <ranish@nvidia.com>
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
 lib/librte_net/rte_ecpri.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/librte_net/rte_ecpri.h b/lib/librte_net/rte_ecpri.h
index d1c4838..1cbd6d8 100644
--- a/lib/librte_net/rte_ecpri.h
+++ b/lib/librte_net/rte_ecpri.h
@@ -167,7 +167,7 @@ struct rte_ecpri_combined_msg_hdr {
 		struct rte_ecpri_msg_iq_data type0;
 		struct rte_ecpri_msg_bit_seq type1;
 		struct rte_ecpri_msg_rtc_ctrl type2;
-		struct rte_ecpri_msg_bit_seq type3;
+		struct rte_ecpri_msg_gen_data type3;
 		struct rte_ecpri_msg_rm_access type4;
 		struct rte_ecpri_msg_delay_measure type5;
 		struct rte_ecpri_msg_remote_reset type6;
-- 
1.8.3.1


             reply	other threads:[~2020-11-23 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 12:29 Viacheslav Ovsiienko [this message]
2020-11-23 12:46 ` Bing Zhao
2020-11-23 14:39   ` Ferruh Yigit
2020-11-26  0:15     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=1606134581-10742-1-git-send-email-viacheslavo@nvidia.com \
    --to=viacheslavo@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ranish@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).