forked from Minki/linux
189e19e8cb
It is misleading to call a functional resource a "device". In adopting the Linux Driver Model, the struct device will be embedded in struct nubus_board. That will compound the terminlogy problem because drivers will bind with boards, not with functional resources. Avoid this by renaming struct nubus_dev as struct nubus_rsrc. "Functional resource" is the vendor's terminology so this helps avoid confusion. Cc: "David S. Miller" <davem@davemloft.net> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Tested-by: Stan Johnson <userm57@yahoo.com> Signed-off-by: Finn Thain <fthain@telegraphics.com.au> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> |
||
---|---|---|
.. | ||
8390.c | ||
8390.h | ||
8390p.c | ||
apne.c | ||
ax88796.c | ||
axnet_cs.c | ||
etherh.c | ||
hydra.c | ||
Kconfig | ||
lib8390.c | ||
mac8390.c | ||
Makefile | ||
mcf8390.c | ||
ne2k-pci.c | ||
ne.c | ||
pcnet_cs.c | ||
smc-ultra.c | ||
stnic.c | ||
wd.c | ||
zorro8390.c |