Hey Martyn,
This is the resend of the patches with the recommended fixes. Some notes
on the various patches:
staging: vme: allow explicit assignment of bus numbers
I have left this as it is with a simple array of numbers. I think we should
apply this for now and work on the UUID method separately as this solves a
major issue in a relatively decent way.
staging: vme: make [alloc|free]_consistent bridge specific
Added the bridge names to the prink's.
staging: vme: add functions for bridge module refcounting
I have added calls in probe and remove to automatically refcount the devices
that are probed. I have left symbol exports for the refcounting functions if
any drivers want to use them in some unforseen way.
staging: vme: add struct vme_dev for VME devices
staging: vme: make match() driver specific to improve non-VME64x
support
Fixes based on the changes introduced before. Note that I have removed the
patch with the rename of the vme_slot_get function. Also removed the
kzalloc patch as it can be applied from the previous send.
Another note: I have not added the documentation yet. Based on the changes
that are approved, I will write it up today and send it in :)
Looking forward to your feedback. Thanks!
--
/manohar
Emilio G. Cota (1):
staging: vme: allow explicit assignment of bus numbers
Manohar Vanga (5):
staging: vme: make [alloc|free]_consistent bridge specific
staging: vme: keep track of registered buses
staging: vme: add functions for bridge module refcounting
staging: vme: add struct vme_dev for VME devices
staging: vme: make match() driver specific to improve non-VME64x
support
drivers/staging/vme/bridges/vme_ca91cx42.c | 46 +++
drivers/staging/vme/bridges/vme_tsi148.c | 47 +++
drivers/staging/vme/devices/vme_user.c | 39 ++-
drivers/staging/vme/devices/vme_user.h | 2 +-
drivers/staging/vme/vme.c | 418 ++++++++++++++++------------
drivers/staging/vme/vme.h | 56 +++-
drivers/staging/vme/vme_bridge.h | 17 +-
7 files changed, 419 insertions(+), 206 deletions(-)
--
1.7.4.1
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
