summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorTom Herbert <tom@herbertland.com>2016-05-18 18:06:09 +0200
committerDavid S. Miller <davem@davemloft.net>2016-05-21 00:03:15 +0200
commit5c7cdf339af560f980b12eb6b0b5aa5f68ac6658 (patch)
tree52b8e3c7b4e57e1379d24587023083302af9ce4c /crypto
parentRevert "phy: add support for a reset-gpio specification" (diff)
downloadlinux-5c7cdf339af560f980b12eb6b0b5aa5f68ac6658.tar.xz
linux-5c7cdf339af560f980b12eb6b0b5aa5f68ac6658.zip
gso: Remove arbitrary checks for unsupported GSO
In several gso_segment functions there are checks of gso_type against a seemingly arbitrary list of SKB_GSO_* flags. This seems like an attempt to identify unsupported GSO types, but since the stack is the one that set these GSO types in the first place this seems unnecessary to do. If a combination isn't valid in the first place that stack should not allow setting it. This is a code simplication especially for add new GSO types. Signed-off-by: Tom Herbert <tom@herbertland.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions