[ARM] Orion: avoid setting ->force_phy_addr

Browse source

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>

...

This commit is contained in:

Lennert Buytenhek 2008-05-28 16:17:39 +02:00 • committed by Lennert Buytenhek

parent b206ed0462

commit 2850a03773

5 changed files with 0 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

arch/arm/mach-orion5x/db88f5281-setup.c

View file

1

arch/arm/mach-orion5x/dns323-setup.c

View file

1

arch/arm/mach-orion5x/kurobox_pro-setup.c

View file

1

arch/arm/mach-orion5x/rd88f5182-setup.c

View file

1

arch/arm/mach-orion5x/ts209-setup.c

View file