diff options
author | 2022-05-02 10:30:36 +0200 | |
---|---|---|
committer | 2022-05-02 10:30:36 +0200 | |
commit | 0f0c0452bbd46d713eeb8968f5f40ccc257f85eb (patch) | |
tree | aac9db6af288e593edb6fb6355c6c9d6a1e5dbc1 /drivers/net/phy/phy.c | |
parent | Merge branch 'adin1100-industrial-PHY-support' (diff) | |
parent | ip6_gre: Make IP6GRE and IP6GRETAP devices always NETIF_F_LLTX (diff) | |
download | wireguard-linux-0f0c0452bbd46d713eeb8968f5f40ccc257f85eb.tar.xz wireguard-linux-0f0c0452bbd46d713eeb8968f5f40ccc257f85eb.zip |
Merge branch 'devices-always-netif_f_lltx'
Peilin Ye says:
====================
devices always NETIF_F_LLTX
v1: https://lore.kernel.org/netdev/cover.1650580763.git.peilin.ye@bytedance.com/
change since v1:
- deleted "depends on patch..." in [1/2]'s commit message
This patchset depends on these fixes [1], which has been merged into
net-next. Since o_seqno is now atomic_t, we can always turn on
NETIF_F_LLTX for [IP6]GRE[TAP] devices, since we no longer need the TX
lock (&txq->_xmit_lock).
We could probably do the same thing to [IP6]ERSPAN devices as well, but
I'm not familiar with them yet. For example, ERSPAN devices are
initialized as |= GRE_FEATURES in erspan_tunnel_init(), but I don't see
IP6ERSPAN devices being initialized as |= GRE6_FEATURES. Where should we
initialize IP6ERSPAN devices' ->features? Please suggest if I'm missing
something, thanks!
[1] https://lore.kernel.org/netdev/cover.1650575919.git.peilin.ye@bytedance.com/
====================
Link: https://lore.kernel.org/r/cover.1651207788.git.peilin.ye@bytedance.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'drivers/net/phy/phy.c')
0 files changed, 0 insertions, 0 deletions