I am really sorry about the exterme number of patches I gave you, it was a very large file to take care of I could make the number of patches a little less if you want. The patches start off simple by taking care of trivial stuff like alignment and space after casts. The patches go into the camel cases. The camel cases are grouped based on the name of the function or structs they are in. If they don't belong to one then they get a patch on their own. Last but not least the typedefs are done and the array checks are fixed Jeffrey (71): staging: unisys: space after a cast visorchipset_main.c staging: unisys: Alignment fixes visorchipset_main.c staging: unisys: visorchipset_main.c logical continuations staging: unisys: kzalloc visorchipset_main.c staging: unisys: visorchipset_main.c braces and spaces staging: unisys: Poll_jiffies camel case staging: unisys: Most_recent_message_jiffies staging: unisys: Periodic_controlvm_work camel case stating: unisys: Periodic_controlvm_workqueue camel case staging: unisys: NotifierLock camel case staging: unisys: controlvm_message_header camel case staging: unisys: static const uuid_le camel case staging: unisys: invalid bus/device number camel cases staging: unisys: controlvm_message_packet camel case staging: unisys: LIST_HEAD info list camel cases staging: unisys: Controlvm_channel camel case staging: unisys: Test_Vnic_channel camel case staging: unisys: LIVEDUMP_INFO camel cases staging: unisys: Controlvm_payload_info camel case staging: unisys: Livedump_info camel case staging: unisys: Controlvm_pending_msg camel case staging: unisys: Putfile_buffer_list_pool_name camel case staging: unisys: Putfile_buffer_list_pool camel case staging: unisys: Putfile_request_list camel case staging: unisys: atomic_t camel case staging: unisys: Parahotplug_request_list camel case staging: unisys: visorchipset_busdev_notifiers camel cases staging: unisys: bus_create_response camel cases staging: unisys: bus_destroy_response camel cases staging: unisys: device_create_response camel cases staging: unisys: device_destroy_response camel cases staging: unisys: device_resume_response camel cases staging: unisys: BusDev_Responders camel case staging: unisys: Controlvm_Pending_Msg_Valid camel case staging: unisys: Parahotplug_request_list_lock camel case staging: unisys: MajorDev camel case staging: unisys: platform_device camel case staging: unisys: controlvm prototype camel cases staging: unisys: toolAction camel cases staging: unisys: efisparindication camel cases staging: unisys: textId camel cases staging: unisys: remainingSteps camel cases staging: unisys: busInfo_clear camel cases staging: unisys: devInfo_clear camel case staging: unisys: chipset_init camel cases staging: unisys: controlvm camel cases staging: unisys: visorchipset_save_message camel cases staging: unisys: bus_responder camel case staging: unisys: device_changestate_responder camel cases staging: unisys: device_responder camel cases staging: unisys: bus_epilog camel cases staging: unisys: device_epilog camel case staging: unisys: bus_create camel cases staging: unisys: bus_destroy camel cases staging: unisys: bus_configure camel case staging: unisys: my_device_create camel cases staging: unisys: my_device_changestate camel case staging: unisys: my_device_destroy camel cases staging: unisys: initialize_controlvm_payload_info camel case staging: unisys: initialize_controlvm_payload camel case staging: unisys: chipset camel cases staging: unisys: handle_command camel cases staging: unisys: controlvm_periodic_work camel cases staging: unisys: setup_crash_devices_work_queue camel cases staging: unisys: visorchipset_init camel cases staging: unisys: testUnicode camel case staging: unisys: Unnecessary parentheses staging: unisys: MESSAGE_ENVELOPE typedef staging: unisys: CONTROLVM_PAYLOAD_INFO typedef staging: unisys: LIVEDUMP_INFO typedef staging: unisys: static const chars visorchipset_main.c .../unisys/visorchipset/visorchipset_main.c | 1270 ++++++++++---------- 1 file changed, 639 insertions(+), 631 deletions(-) -- 1.8.4 _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
