1. 28 Feb, 2015 7 commits
  2. 23 Feb, 2015 1 commit
    • Roopa Prabhu's avatar
      bridge: add vlan info to bridge setlink and dellink notification messages · b7853d73
      Roopa Prabhu authored
      vlan add/deletes are not notified to userspace today. This patch adds
      vlan info to bridge newlink/dellink notifications generated from the
      bridge driver. Notifications use the RTEXT_FILTER_BRVLAN_COMPRESSED
      flag to compress vlans into ranges whereever applicable.
      
      The size calculations does not take ranges into account for
      simplicity.  This has the potential for allocating a larger skb than
      required.
      
      There is an existing inconsistency with bridge NEWLINK and DELLINK
      change notifications. Both generate NEWLINK notifications.  Since its
      always a NEWLINK notification, this patch includes all vlans the port
      belongs to in the notification. The NEWLINK and DELLINK request
      messages however only include the vlans to be added and deleted.
      Signed-off-by: default avatarRoopa Prabhu <roopa@cumulusnetworks.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b7853d73
  3. 22 Feb, 2015 8 commits
  4. 20 Feb, 2015 23 commits
  5. 19 Feb, 2015 1 commit
    • David S. Miller's avatar
      Merge branch 'mv88e6171_indirect_phy' · 69994d17
      David S. Miller authored
      Andrew Lunn says:
      
      ====================
      Indirect phy access for mv88e6171
      
      These two patches allow the mv88e6171 driver to access the port phys
      using indirect addressing. Depending on pin strapping, the switch
      either uses a single address on the host MDIO bus, requiring the port
      phys are accessed indirectly, or the switch uses a number of addresses
      on the host bus and the phys can be directly accessed.
      
      The 370RD, the first supported platform to use the 6171 uses multiple
      addresses, so this indirect mode was not required. However the
      WRT1900AC has the switch configured to use a single address, and so
      indirect access is needed.
      
      The mv88e6352 already has all the needed code. Refactor it into the
      shared mv88e6xxx and then use it in the mv88e6171 driver.
      
      Tested on the 370RD and WRT1900AC.
      
      It would be good if Guenter Roeck could test on his platform to ensure
      i've not broken anything for the mv88e6352.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      69994d17