summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorIan Morgan <imorgan@primordial.ca>2014-10-19 08:05:13 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-11-14 08:47:53 -0800
commit9744aac69371ecac7ac6bef8a7a4a65d4e949dfa (patch)
tree2e52641c8749e010262fd0a2585be8c2231074f8 /net
parent4449361e6feca3caa91749ad3f8333f9ac5502ab (diff)
downloadlinux-3.10-9744aac69371ecac7ac6bef8a7a4a65d4e949dfa.tar.gz
linux-3.10-9744aac69371ecac7ac6bef8a7a4a65d4e949dfa.tar.bz2
linux-3.10-9744aac69371ecac7ac6bef8a7a4a65d4e949dfa.zip
ax88179_178a: fix bonding failure
[ Upstream commit 95ff88688781db2f64042e69bd499e518bbb36e5 ] The following patch fixes a bug which causes the ax88179_178a driver to be incapable of being added to a bond. When I brought up the issue with the bonding maintainers, they indicated that the real problem was with the NIC driver which must return zero for success (of setting the MAC address). I see that several other NIC drivers follow that pattern by either simply always returing zero, or by passing through a negative (error) result while rewriting any positive return code to zero. With that same philisophy applied to the ax88179_178a driver, it allows it to work correctly with the bonding driver. I believe this is suitable for queuing in -stable, as it's a small, simple, and obvious fix that corrects a defect with no other known workaround. This patch is against vanilla 3.17(.0). Signed-off-by: Ian Morgan <imorgan@primordial.ca> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions