diff options
| author | Radu Rendec <rrendec@redhat.com> | 2024-12-19 11:36:05 -0500 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2024-12-23 10:11:04 -0800 |
| commit | 46e0ccfb88f02ab2eb20a41d519d6e4c028652f2 (patch) | |
| tree | 49f54792f2e2a2b1ce3af10486a4a0bd2bf78fd6 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | 6ad7f7196a732d960a264f32aa2d052f260f9f0c (diff) | |
| download | linux-46e0ccfb88f02ab2eb20a41d519d6e4c028652f2.tar.gz linux-46e0ccfb88f02ab2eb20a41d519d6e4c028652f2.tar.bz2 linux-46e0ccfb88f02ab2eb20a41d519d6e4c028652f2.zip | |
net: vxlan: rename SKB_DROP_REASON_VXLAN_NO_REMOTE
The SKB_DROP_REASON_VXLAN_NO_REMOTE skb drop reason was introduced in
the specific context of vxlan. As it turns out, there are similar cases
when a packet needs to be dropped in other parts of the network stack,
such as the bridge module.
Rename SKB_DROP_REASON_VXLAN_NO_REMOTE and give it a more generic name,
so that it can be used in other parts of the network stack. This is not
a functional change, and the numeric value of the drop reason even
remains unchanged.
Signed-off-by: Radu Rendec <rrendec@redhat.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
Link: https://patch.msgid.link/20241219163606.717758-2-rrendec@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions