netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Camelia Groza <camelia.groza@nxp.com>
To: kuba@kernel.org, brouer@redhat.com, saeed@kernel.org,
	davem@davemloft.net
Cc: madalin.bucur@oss.nxp.com, ioana.ciornei@nxp.com,
	netdev@vger.kernel.org, Camelia Groza <camelia.groza@nxp.com>
Subject: [PATCH net-next v3 6/7] dpaa_eth: rename current skb A050385 erratum workaround
Date: Thu, 19 Nov 2020 18:29:35 +0200	[thread overview]
Message-ID: <454f789a87f44af29db4d83277fb7e81e6be0b76.1605802951.git.camelia.groza@nxp.com> (raw)
In-Reply-To: <cover.1605802951.git.camelia.groza@nxp.com>
In-Reply-To: <cover.1605802951.git.camelia.groza@nxp.com>

Explicitly point that the current workaround addresses skbs. This change is
in preparation for adding a workaround for XDP scenarios.

Acked-by: Madalin Bucur <madalin.bucur@oss.nxp.com>
Signed-off-by: Camelia Groza <camelia.groza@nxp.com>
---
 drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
index 3214ea0..b9d46e6 100644
--- a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
+++ b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
@@ -2105,7 +2105,7 @@ static inline int dpaa_xmit(struct dpaa_priv *priv,
 }
 
 #ifdef CONFIG_DPAA_ERRATUM_A050385
-static int dpaa_a050385_wa(struct net_device *net_dev, struct sk_buff **s)
+static int dpaa_a050385_wa_skb(struct net_device *net_dev, struct sk_buff **s)
 {
 	struct dpaa_priv *priv = netdev_priv(net_dev);
 	struct sk_buff *new_skb, *skb = *s;
@@ -2221,7 +2221,7 @@ static int dpaa_a050385_wa(struct net_device *net_dev, struct sk_buff **s)
 
 #ifdef CONFIG_DPAA_ERRATUM_A050385
 	if (unlikely(fman_has_errata_a050385())) {
-		if (dpaa_a050385_wa(net_dev, &skb))
+		if (dpaa_a050385_wa_skb(net_dev, &skb))
 			goto enomem;
 		nonlinear = skb_is_nonlinear(skb);
 	}
-- 
1.9.1


  parent reply	other threads:[~2020-11-19 16:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 16:29 [PATCH net-next v3 0/7] dpaa_eth: add XDP support Camelia Groza
2020-11-19 16:29 ` [PATCH net-next v3 1/7] dpaa_eth: add struct for software backpointers Camelia Groza
2020-11-19 16:29 ` [PATCH net-next v3 2/7] dpaa_eth: add basic XDP support Camelia Groza
2020-11-20  0:18   ` Maciej Fijalkowski
2020-11-20 18:50     ` Camelia Alexandra Groza
2020-11-23 22:07       ` Maciej Fijalkowski
2020-11-24 13:47         ` Camelia Alexandra Groza
2020-11-19 16:29 ` [PATCH net-next v3 3/7] dpaa_eth: limit the possible MTU range when XDP is enabled Camelia Groza
2020-11-19 16:29 ` [PATCH net-next v3 4/7] dpaa_eth: add XDP_TX support Camelia Groza
2020-11-19 23:50   ` Maciej Fijalkowski
2020-11-20 18:54     ` Camelia Alexandra Groza
2020-11-23 22:18       ` Maciej Fijalkowski
2020-11-24 13:06         ` Camelia Alexandra Groza
2020-11-19 16:29 ` [PATCH net-next v3 5/7] dpaa_eth: add XDP_REDIRECT support Camelia Groza
2020-11-19 16:29 ` Camelia Groza [this message]
2020-11-19 16:29 ` [PATCH net-next v3 7/7] dpaa_eth: implement the A050385 erratum workaround for XDP Camelia Groza

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=454f789a87f44af29db4d83277fb7e81e6be0b76.1605802951.git.camelia.groza@nxp.com \
    --to=camelia.groza@nxp.com \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=ioana.ciornei@nxp.com \
    --cc=kuba@kernel.org \
    --cc=madalin.bucur@oss.nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeed@kernel.org \
    /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).