summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorSven Eckelmann <sven@narfation.org>2026-07-30 08:23:28 +0200
committerSven Eckelmann <sven@narfation.org>2026-08-05 10:00:16 +0200
commit02aee8ebea3a714d92b27da9a9d8791d8c8c9a4f (patch)
tree7b347e7e2e2f3c94ec21d635718bdc7361f1745b /tools/perf/scripts/python/bin/stackcollapse-record
parent1c852e4a99c732dc7e93a0aee195d10eba1f6339 (diff)
batman-adv: remove negative returns for batadv_send_skb_unicast
The kernel documentation for batadv_send_skb_unicast() states that only the return values NET_XMIT_DROP and NET_XMIT_SUCCESS are valid. Functions like batadv_dat_snoop_incoming_arp_request() are only checking if the return is not NET_XMIT_DROP to check if send was successful or not. Negative values were therefore also handled as success. Similar functions are not returning the batadv_send_skb_to_orig() return value directly but are checking if it is a direct success and only then marking the return as such. This must also be adopted for batadv_send_skb_unicast(). The callers of this function are mostly not affected. Only packet counting in batadv_dat_snoop_incoming_arp_request() will now work as expected in case of a negative return value from batadv_send_skb_to_orig(). Signed-off-by: Sven Eckelmann <sven@narfation.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions