Hi Ionut, On Sun, Nov 21, 2010 at 4:46 AM, Ionut Nicu <ionut.nicu@xxxxxxxxx> wrote: > This set of patches replaces some of the redundant components of > the tidspbridge driver, such as: > > * wrapper functions for kmalloc/kfree > * custom bitmap implementation > * custom linked list implementation (list_head wrapper) > > with the standard linux kernel interfaces. > > The patches also do some code reorganization for increasing readability. > Most of the changes reduce the code indentation level and simplify the code. > No functional changes were done. > > There are many places in this driver that need this kind of cleanup, but > these patches only fix the functions that were touched while converting > the code to use linux bitmap and list_head. Thanks for your patches, I just fixed the style of some multiline comments before pushing, since these are very minor fixes I avoided the noise of resending the patches. Please remember to follow the Coding Style for multi line comments whenever you insert back those lines (even if the code was that way). > Ionut Nicu (12): > staging: tidspbridge: remove gs memory allocator > staging: tidspbridge: remove utildefs > staging: tidspbridge: switch to linux bitmap API > staging: tidspbridge: remove gb bitmap implementation Pushed > staging: tidspbridge: rmgr/node.c code cleanup Changes requested > staging: tidspbridge: convert core to list_head Fixed a multiline style comment > staging: tidspbridge: convert pmgr to list_head Fixed 2 multiline style comment > staging: tidspbridge: convert rmgr to list_head > staging: tidspbridge: remove custom linked list Pushed > staging: tidspbridge: core code cleanup Fixed multiline style comments > staging: tidspbridge: pmgr code cleanup Fixed multiline style comments > staging: tidspbridge: rmgr code cleanup Doesn't apply because of patch "staging: tidspbridge: rmgr/node.c code cleanup" was not pushed. Regards, Omar -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
