summaryrefslogtreecommitdiff
path: root/drivers/irqchip/exynos-combiner.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2022-05-06 12:07:56 +0100
committerDavid S. Miller <davem@davemloft.net>2022-05-06 12:07:56 +0100
commit95730d65708397828f75ca7dbca838edf6727bfd (patch)
tree37f896eb09e44bcaaa344a03a96052843a4dbd90 /drivers/irqchip/exynos-combiner.c
parentbeb21e3e8e261fc9f11050af17efe6de183b33d3 (diff)
parent744d49daf8bd3b17b345c836f2e6f97d49fa6ae8 (diff)
Merge branch 'tso-gso-limit-split'
Jakub Kicinski says: ==================== net: disambiguate the TSO and GSO limits This series separates the device-reported TSO limitations from the user space-controlled GSO limits. It used to be that we only had the former (HW limits) but they were named GSO. This probably lead to confusion and letting user override them. The problem came up in the BIG TCP discussion between Eric and Alex, and seems like something we should address. Targeting net-next because (a) nobody is reporting problems; and (b) there is a tiny but non-zero chance that some actually wants to lift the HW limitations. ==================== Reviewed-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/irqchip/exynos-combiner.c')
0 files changed, 0 insertions, 0 deletions