aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/memstick
diff options
context:
space:
mode:
authorFinn Thain <fthain@telegraphics.com.au>2018-01-13 17:37:13 -0500
committerGeert Uytterhoeven <geert@linux-m68k.org>2018-01-16 16:47:29 +0100
commit189e19e8cbb49f5bf483e55bdbd1e56d3d6bcf75 (patch)
tree8965cd03d125100f4788e69d2be0fcf92d31ed1f /drivers/memstick
parentnubus: Rework /proc/bus/nubus/s/ implementation (diff)
downloadlinux-dev-189e19e8cbb49f5bf483e55bdbd1e56d3d6bcf75.tar.xz
linux-dev-189e19e8cbb49f5bf483e55bdbd1e56d3d6bcf75.zip
nubus: Rename struct nubus_dev
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>
Diffstat (limited to 'drivers/memstick')
0 files changed, 0 insertions, 0 deletions