summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-orion5x/kurobox_pro-setup.c
diff options
context:
space:
mode:
authorLennert Buytenhek <buytenh@wantstofly.org>2008-05-28 16:17:39 +0200
committerLennert Buytenhek <buytenh@marvell.com>2008-06-22 22:44:48 +0200
commit2850a037734eac0af2e6abc4e8be986c3edfd834 (patch)
treeab0e8a470dc8464fff2452b2580cc41b397a8ccc /arch/arm/mach-orion5x/kurobox_pro-setup.c
parentb206ed0462b7112d07bb9f245bf49f5e95ff174a (diff)
downloadlinux-2850a037734eac0af2e6abc4e8be986c3edfd834.tar.gz
linux-2850a037734eac0af2e6abc4e8be986c3edfd834.tar.bz2
linux-2850a037734eac0af2e6abc4e8be986c3edfd834.zip
[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>
Diffstat (limited to 'arch/arm/mach-orion5x/kurobox_pro-setup.c')
-rw-r--r--arch/arm/mach-orion5x/kurobox_pro-setup.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/mach-orion5x/kurobox_pro-setup.c b/arch/arm/mach-orion5x/kurobox_pro-setup.c
index b8414f6e0e83..8b4a8aa5a836 100644
--- a/arch/arm/mach-orion5x/kurobox_pro-setup.c
+++ b/arch/arm/mach-orion5x/kurobox_pro-setup.c
@@ -158,7 +158,6 @@ subsys_initcall(kurobox_pro_pci_init);
static struct mv643xx_eth_platform_data kurobox_pro_eth_data = {
.phy_addr = 8,
- .force_phy_addr = 1,
};
/*****************************************************************************