summaryrefslogtreecommitdiff
path: root/drivers/mmc/host/tifm_sd.c
diff options
context:
space:
mode:
authorHerbert Xu <herbert@gondor.apana.org.au>2007-08-21 10:22:55 +0400
committerGreg Kroah-Hartman <gregkh@suse.de>2007-08-31 10:01:00 +0400
commitd5e756e26a271662bab6a10df75f2b3f9bc54ef7 (patch)
treea02ba807e242dbccab2e35fddb1c608a1f18a3ac /drivers/mmc/host/tifm_sd.c
parent1db5759e2d29c90d99659e132d4a137e20460061 (diff)
downloadlinux-d5e756e26a271662bab6a10df75f2b3f9bc54ef7.tar.xz
NET: Share correct feature code between bridging and bonding
[NET]: Share correct feature code between bridging and bonding http://bugzilla.kernel.org/show_bug.cgi?id=8797 shows that the bonding driver may produce bogus combinations of the checksum flags and SG/TSO. For example, if you bond devices with NETIF_F_HW_CSUM and NETIF_F_IP_CSUM you'll end up with a bonding device that has neither flag set. If both have TSO then this produces an illegal combination. The bridge device on the other hand has the correct code to deal with this. In fact, the same code can be used for both. So this patch moves that logic into net/core/dev.c and uses it for both bonding and bridging. In the process I've made small adjustments such as only setting GSO_ROBUST if at least one constituent device supports it. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Acked-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/mmc/host/tifm_sd.c')
0 files changed, 0 insertions, 0 deletions