DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gagandeep Singh <g.singh@nxp.com>
To: ferruh.yigit@amd.com, dev@dpdk.org, jiawenwu@trustnetic.com,
	hemant.agrawal@nxp.com
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: [PATCH 2/2] net/ngbe: use new IEEE1588 flags
Date: Wed, 28 Sep 2022 12:44:06 +0530	[thread overview]
Message-ID: <20220928071406.1532345-2-g.singh@nxp.com> (raw)
In-Reply-To: <20220928071406.1532345-1-g.singh@nxp.com>

Flags for IEEE1588 with ``PKT_*`` prefix has been changed to
``RTE_MBUF_F_*``. So in this patch updating the
old flags.

Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
---
 drivers/net/ngbe/ngbe_rxtx.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/net/ngbe/ngbe_rxtx.c b/drivers/net/ngbe/ngbe_rxtx.c
index 86a5ef5486..9fd24fa444 100644
--- a/drivers/net/ngbe/ngbe_rxtx.c
+++ b/drivers/net/ngbe/ngbe_rxtx.c
@@ -17,7 +17,7 @@
 #include "ngbe_rxtx.h"
 
 #ifdef RTE_LIBRTE_IEEE1588
-#define NGBE_TX_IEEE1588_TMST PKT_TX_IEEE1588_TMST
+#define NGBE_TX_IEEE1588_TMST RTE_MBUF_F_TX_IEEE1588_TMST
 #else
 #define NGBE_TX_IEEE1588_TMST 0
 #endif
@@ -740,7 +740,7 @@ ngbe_xmit_pkts(void *tx_queue, struct rte_mbuf **tx_pkts,
 		cmd_type_len = NGBE_TXD_FCS;
 
 #ifdef RTE_LIBRTE_IEEE1588
-		if (ol_flags & PKT_TX_IEEE1588_TMST)
+		if (ol_flags & RTE_MBUF_F_TX_IEEE1588_TMST)
 			cmd_type_len |= NGBE_TXD_1588;
 #endif
 
@@ -922,7 +922,7 @@ ngbe_rxd_pkt_info_to_pkt_flags(uint32_t pkt_info)
 	};
 #ifdef RTE_LIBRTE_IEEE1588
 	static uint64_t ip_pkt_etqf_map[8] = {
-		0, 0, 0, PKT_RX_IEEE1588_PTP,
+		0, 0, 0, RTE_MBUF_F_RX_IEEE1588_PTP,
 		0, 0, 0, 0,
 	};
 	int etfid = ngbe_etflt_id(NGBE_RXD_PTID(pkt_info));
@@ -952,7 +952,7 @@ rx_desc_status_to_pkt_flags(uint32_t rx_status, uint64_t vlan_flags)
 
 #ifdef RTE_LIBRTE_IEEE1588
 	if (rx_status & NGBE_RXD_STAT_1588)
-		pkt_flags = pkt_flags | PKT_RX_IEEE1588_TMST;
+		pkt_flags = pkt_flags | RTE_MBUF_F_RX_IEEE1588_TMST;
 #endif
 	return pkt_flags;
 }
-- 
2.25.1


  reply	other threads:[~2022-09-28  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  7:14 [PATCH 1/2] net/dpaa2: " Gagandeep Singh
2022-09-28  7:14 ` Gagandeep Singh [this message]
2022-09-28  9:08   ` [PATCH 2/2] net/ngbe: " Jiang, YuX
2022-10-04  0:10 ` [PATCH 1/2] net/dpaa2: " Ferruh Yigit

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=20220928071406.1532345-2-g.singh@nxp.com \
    --to=g.singh@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jiawenwu@trustnetic.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).