This series primarily concentrates on adding additional error handling so that the s-Par drivers can correctly handle the errors at a centralized location instead of doing it inconsistently scattered throughout the source tree. David Kershner (43): staging: unisys: visorbus: parahotplug_process_message add error handling staging: unisys: visorbus: add error handling to handle_command staging: unisys: visorbus: add error handling to controlvm_periodic_work staging: unisys: visorbus: add error handling for parahotplug_request_kickoff staging: unisys: visorbus: add error handling around kobject_uevent staging: unisys: visorbus: add error handling to toolaction_show staging: unisys: visorbus: add error handling to boottotool_show staging: unisys: visorbus: add error handling to error_show staging: unisys: visorbus: add error handling textid_show staging: unisys: visorbus: add error handling to remaining_steps_show staging: unisys: visorbus: move bus_device_info_init to visorbus_main.c staging: unisys: visorbus: remove invalid comment, we are one driver. staging: unisys: visorbus: convert ret to err to be consistent staging: unisys: visorbus: boottotool convert ret to err staging: unisys: visorbus: error_store convert ret to err staging: unisys: visorbus: textid_store convert ret to err staging: unisys: visorbus: remaining_steps convert ret to err staging: unisys: visorbus: add error handling to chipset_bus_create staging: unisys: visornic: add error handling for visorchannel_signalinsert/remove staging: unisys: visorbus: add error handling for chipset_device_create staging: unisys: visorbus: consolidate bus_responder and device_responder staging: unisys: visorbus: move vbuschannel_print_devinfo from .h to .c file staging: unisys: visorbus: get rid of shouting SPAR_VBUS_CHANNEL_CLIENT_OK macro staging: unisys: remove client from spar_check_channel staging: unisys: visorbus: add error handling for dev_start_periodic_work staging: unisys: visorbus: add error handling visorbus_enable_channel_interrupt staging: unisys: visorbus: fix error handling in create_bus_instance staging: unisys: visorbus: get rid of create_bus_type. staging: unisys: visorbus: get rid of unused parameter forcematch staging: unisys: visorbus: get rid of unused parameter forcenomatch staging: unisys: visorbus: cleanup error handling in visorbus_uevent staging: unisys: visorbus: check for err from dev_set_name staging: unisys: visorbus: don't ignore visorchannel_read error staging: unisys: visorbus: don't unregister if we failed to register staging: unisys: visorbus: add error handling to initiate_chipset_device_pause_resume staging: unisys: visorbus: add error handling to chipset_device_pause/resume staging: unisys: visorbus: get rid of braces around single statements staging: unisys: visorbus: consolidate if statements staging: unisys: visorbus: remove useless ifdef staging: unisys: visorbus: get rid of ISSUE_IO_VMCALL staging: unisys: visorbus: Update vmcallinterface comment staging: unisys: visorbus: move unisys_vmcall into visorchipset staging: unisys: visorbus: Have unisys_vmcall return Linux error instead of VMCALL error Sameer Wadgaonkar (1): staging: unisys: visorbus: add __packed to structures in controlvmchannel.h drivers/staging/unisys/include/channel.h | 12 +- drivers/staging/unisys/include/iochannel.h | 16 +- drivers/staging/unisys/include/visorbus.h | 2 +- drivers/staging/unisys/visorbus/controlvmchannel.h | 70 +- drivers/staging/unisys/visorbus/vbuschannel.h | 43 +- drivers/staging/unisys/visorbus/visorbus_main.c | 316 ++++------ drivers/staging/unisys/visorbus/visorbus_private.h | 24 +- drivers/staging/unisys/visorbus/visorchannel.c | 18 +- drivers/staging/unisys/visorbus/visorchipset.c | 458 ++++++++------ drivers/staging/unisys/visorbus/vmcallinterface.h | 41 +- drivers/staging/unisys/visornic/visornic_main.c | 137 ++-- 11 files changed, 595 insertions(+), 542 deletions(-) base-commit: a15505e69cd2f8d0ebf566cd5c5838bd5c2d56e3 -- git-series 0.9.1 _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel