diff options
author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2021-10-20 20:42:20 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2021-10-22 01:35:55 +0300 |
commit | 520661495409666771d6e4be683ce5e4854c60f5 (patch) | |
tree | ea4a4640f3a375748fcce9821ba4b06fd7e236d5 /arch/openrisc | |
parent | ae77bdbc2fc63bdaa58b64ed06c51e4052631902 (diff) | |
download | linux-520661495409666771d6e4be683ce5e4854c60f5.tar.xz |
net: enetc: use the skb variable directly in enetc_clean_tx_ring()
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>
Reviewed-by: Claudiu Manoil <claudiu.manoil@nxp.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'arch/openrisc')
0 files changed, 0 insertions, 0 deletions