diff options
author | Gregory CLEMENT <gregory.clement@bootlin.com> | 2018-07-18 19:10:52 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-07-29 08:12:55 +0300 |
commit | 965cbbec7f207fef969d268fdabbcb779ec294ab (patch) | |
tree | 88ff14d888bcfc46c8ab6eb1e3c5aa22c67957e2 /drivers/dax | |
parent | 8466baf788ec3e18836bd9c91ba0b1a07af25878 (diff) | |
download | linux-965cbbec7f207fef969d268fdabbcb779ec294ab.tar.xz |
net: mvneta: remove data pointer usage from device_node structure
On year ago Rob Herring wanted to remove the data pointer from the
device_node structure[1]. The mvneta driver seemed to be the only one
which used (abused ?) it. However, the proposal of Rob to remove this
pointer from the driver introduced a regression, and I tested and fixed an
alternative way, but it was never submitted as a proper patch.
Now here it is: Instead of using the device_node structure ->data
pointer, we store the BM private data as the driver data of the BM
platform_device. The core mvneta code can retrieve it by doing a lookup
on which platform_device corresponds to the BM device tree node using
of_find_device_by_node(), and get its driver data
[1]https://www.spinics.net/lists/netdev/msg445197.html
Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions