| commit | 84dd619e4dc3b0b1c40dafd98c90fd950bce7bc5 | |
| author | Dale Farnsworth <dale@farnsworth.org> | |
| Sat, 3 Mar 2007 13:40:28 +0000 (3 06:40 -0700) | ||
| committer | Jeff Garzik <jeff@garzik.org> | |
| Tue, 6 Mar 2007 11:14:54 +0000 (6 06:14 -0500) | ||
| tree | 939d601f7abda95e3f4919af2a371873f0c66928 | treesnapshot (tar.gz zip) |
| parent | b2cbbd8e0e8093fbf115ac2669482b016d781c78 | commitdiff |
mv643xx_eth: Place explicit port number in mv643xx_eth_platform_data
We were using the platform_device.id field to identify which ethernet
port is used for mv643xx_eth device. This is not generally correct.
It will be incorrect, for example, if a hardware platform uses a single
port but not the first port. Here, we add an explicit port_number field
to struct mv643xx_eth_platform_data.
This makes the mv643xx_eth_platform_data structure required, but that
isn't an issue since all users currently provide it already.
Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
We were using the platform_device.id field to identify which ethernet
port is used for mv643xx_eth device. This is not generally correct.
It will be incorrect, for example, if a hardware platform uses a single
port but not the first port. Here, we add an explicit port_number field
to struct mv643xx_eth_platform_data.
This makes the mv643xx_eth_platform_data structure required, but that
isn't an issue since all users currently provide it already.
Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
Signed-off-by: Jeff Garzik <jeff@garzik.org>