[ARM] Orion: avoid setting ->force_phy_addr
authorLennert Buytenhek <buytenh@wantstofly.org>
Wed, 28 May 2008 14:17:39 +0000 (16:17 +0200)
committerLennert Buytenhek <buytenh@marvell.com>
Sun, 22 Jun 2008 20:44:48 +0000 (22:44 +0200)
commit2850a037734eac0af2e6abc4e8be986c3edfd834
treeab0e8a470dc8464fff2452b2580cc41b397a8ccc
parentb206ed0462b7112d07bb9f245bf49f5e95ff174a
[ARM] Orion: avoid setting ->force_phy_addr

The mv643xx_eth platform data field ->force_phy_addr only needs
to be set if the passed-in ->phy_addr field is zero (to distinguish
the case of not having specified a phy address
(force_phy_addr = 0) from the case where a phy address of zero needs
to be used (force_phy_addr = 1.))

Also, the ->force_phy_addr field will hopefully disappear in a
future mv643xx_eth reorganisation.

Therefore, this patch deletes the ->force_phy_addr field initialiser
from all Orion board code.

Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
arch/arm/mach-orion5x/db88f5281-setup.c
arch/arm/mach-orion5x/dns323-setup.c
arch/arm/mach-orion5x/kurobox_pro-setup.c
arch/arm/mach-orion5x/rd88f5182-setup.c
arch/arm/mach-orion5x/ts209-setup.c