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 1/2] net/dpaa2: use new IEEE1588 flags
Date: Wed, 28 Sep 2022 12:44:05 +0530 [thread overview]
Message-ID: <20220928071406.1532345-1-g.singh@nxp.com> (raw)
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/dpaa2/dpaa2_rxtx.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/dpaa2/dpaa2_rxtx.c b/drivers/net/dpaa2/dpaa2_rxtx.c
index 9436a95ac8..ebb972c358 100644
--- a/drivers/net/dpaa2/dpaa2_rxtx.c
+++ b/drivers/net/dpaa2/dpaa2_rxtx.c
@@ -814,7 +814,7 @@ dpaa2_dev_prefetch_rx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
else
bufs[num_rx] = eth_fd_to_mbuf(fd, eth_data->port_id);
#if defined(RTE_LIBRTE_IEEE1588)
- if (bufs[num_rx]->ol_flags & PKT_RX_IEEE1588_TMST) {
+ if (bufs[num_rx]->ol_flags & RTE_MBUF_F_RX_IEEE1588_TMST) {
priv->rx_timestamp =
*dpaa2_timestamp_dynfield(bufs[num_rx]);
}
@@ -1035,7 +1035,7 @@ dpaa2_dev_rx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
eth_data->port_id);
#if defined(RTE_LIBRTE_IEEE1588)
- if (bufs[num_rx]->ol_flags & PKT_RX_IEEE1588_TMST) {
+ if (bufs[num_rx]->ol_flags & RTE_MBUF_F_RX_IEEE1588_TMST) {
priv->rx_timestamp =
*dpaa2_timestamp_dynfield(bufs[num_rx]);
}
@@ -1166,7 +1166,7 @@ uint16_t dpaa2_dev_tx_conf(void *queue)
mbuf = DPAA2_INLINE_MBUF_FROM_BUF(v_addr,
rte_dpaa2_bpid_info[DPAA2_GET_FD_BPID(fd)].meta_data_size);
- if (mbuf->ol_flags & PKT_TX_IEEE1588_TMST) {
+ if (mbuf->ol_flags & RTE_MBUF_F_TX_IEEE1588_TMST) {
annotation = (struct dpaa2_annot_hdr *)((size_t)
DPAA2_IOVA_TO_VADDR(DPAA2_GET_FD_ADDR(fd)) +
DPAA2_FD_PTA_SIZE);
@@ -1247,7 +1247,7 @@ dpaa2_dev_tx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
* corresponding to last packet transmitted for reading
* the timestamp
*/
- if ((*bufs)->ol_flags & PKT_TX_IEEE1588_TMST) {
+ if ((*bufs)->ol_flags & RTE_MBUF_F_TX_IEEE1588_TMST) {
priv->next_tx_conf_queue = dpaa2_q->tx_conf_queue;
dpaa2_dev_tx_conf(dpaa2_q->tx_conf_queue);
priv->tx_timestamp = 0;
--
2.25.1
next 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 Gagandeep Singh [this message]
2022-09-28 7:14 ` [PATCH 2/2] net/ngbe: " Gagandeep Singh
2022-09-28 9:08 ` 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-1-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).