summaryrefslogtreecommitdiffstats
path: root/tools/arch/x86/lib
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-11-09 09:26:50 +0900
committerDavid S. Miller <davem@davemloft.net>2017-11-09 09:26:50 +0900
commit19aeeb9f46cb4b9474ebeb50cb01b9a1adba73b8 (patch)
tree4595fb0d4562f8344212e3f0c2842d5ab8a63cfb /tools/arch/x86/lib
parentb2d0f5d5dc53532e6f07bc546a476a55ebdfe0f3 (diff)
parentb4fbb347fe4cd7988d0f9453a7e3ab0cd1b4a75a (diff)
downloadtalos-obmc-linux-19aeeb9f46cb4b9474ebeb50cb01b9a1adba73b8.tar.gz
talos-obmc-linux-19aeeb9f46cb4b9474ebeb50cb01b9a1adba73b8.zip
Merge branch 'dsa-setup-stage'
Vivien Didelot says: ==================== net: dsa: setup stage When probing a DSA switch, there is basically two stages. The first stage is the parsing of the switch device, from either device tree or platform data. It fetches the DSA tree to which it belongs, and validates its ports. The switch device is then added to the tree, and the second stage is called if this was the last switch of the tree. The second stage is the setup of the tree, which validates that the tree is complete, sets up the routing tables, the default CPU port for user ports, sets up the switch drivers and finally the master interfaces, which makes the whole switch fabric functional. This patch series covers the second setup stage. The setup and teardown of a switch tree have been separated into logical steps, and the probing of a switch now simply parses and adds a switch to a tree. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/arch/x86/lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud