From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-10-20 17:42:40
These are two cleanup patches for some inconsistencies I noticed in the
driver's TX ring cleanup function.
Vladimir Oltean (2):
net: enetc: remove local "priv" variable in enetc_clean_tx_ring()
net: enetc: use the skb variable directly in enetc_clean_tx_ring()
drivers/net/ethernet/freescale/enetc/enetc.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
--
2.25.1
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-10-20 17:42:43
The "priv" variable is needed in the "check_writeback" scope since
commit d39823121911 ("enetc: add hardware timestamping support").
Since commit 7294380c5211 ("enetc: support PTP Sync packet one-step
timestamping"), we also need "priv" in the larger function scope.
So the local variable from the "if" block scope is not needed, and
actually shadows the other one. Delete it.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
drivers/net/ethernet/freescale/enetc/enetc.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-10-20 17:42:44
The code checks whether the skb had one-step TX timestamping enabled, in
order to schedule the work item for emptying the priv->tx_skbs queue.
That code checks for "tx_swbd->skb" directly, when we already had a skb
retrieved using enetc_tx_swbd_get_skb(tx_swbd) - a TX software BD can
also hold an XDP_TX packet or an XDP frame. But since the direct tx_swbd
dereference is in an "if" block guarded by the non-NULL quality of
"skb", accessing "tx_swbd->skb" directly is not wrong, just confusing.
Just use the local variable named "skb".
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
drivers/net/ethernet/freescale/enetc/enetc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
@@ -831,8 +831,7 @@ static bool enetc_clean_tx_ring(struct enetc_bdr *tx_ring, int napi_budget)if(xdp_frame){xdp_return_frame(xdp_frame);}elseif(skb){-if(unlikely(tx_swbd->skb->cb[0]&-ENETC_F_TX_ONESTEP_SYNC_TSTAMP)){+if(unlikely(skb->cb[0]&ENETC_F_TX_ONESTEP_SYNC_TSTAMP)){/* Start work to release lock for next one-step*timestampingpacket.Andsendoneskbin*tx_skbsqueueifhas.
-----Original Message-----
From: Vladimir Oltean <vladimir.oltean@nxp.com>
Sent: Wednesday, October 20, 2021 8:42 PM
[...]
Subject: [PATCH net-next 0/2] enetc: trivial PTP one-step TX timestamping
cleanups
These are two cleanup patches for some inconsistencies I noticed in the
driver's TX ring cleanup function.
Vladimir Oltean (2):
net: enetc: remove local "priv" variable in enetc_clean_tx_ring()
net: enetc: use the skb variable directly in enetc_clean_tx_ring()
drivers/net/ethernet/freescale/enetc/enetc.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
--
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski [off-list ref]:
On Wed, 20 Oct 2021 20:42:18 +0300 you wrote:
These are two cleanup patches for some inconsistencies I noticed in the
driver's TX ring cleanup function.
Vladimir Oltean (2):
net: enetc: remove local "priv" variable in enetc_clean_tx_ring()
net: enetc: use the skb variable directly in enetc_clean_tx_ring()
[...]