I recently went through the AOSP common.git android/3.10 tree to try to pull fixes that haven't been submitted upstream. I've cherry picked those patches and submitted them for 3.15, but Greg requested the bugfixes to be submitted by themselves for 3.14.
So here are the subset of changes that are bugfixes. There is one additional patch here which I missed in my last submission, but its a build warning fix, so I think its appropriate. If and when these are merged, I'll resubmit the rest of the queue (which has grown further as of today) for 3.15. Anyway, please let me know if there's any feedback or suggestions. thanks -john Cc: Greg KH <[email protected]> Cc: Colin Cross <[email protected]> Cc: Greg Hackmann <[email protected]> Cc: Prakash Kamliya <[email protected]> Cc: Alistair Strachan <[email protected]> Cc: Todd Poynor <[email protected]> Cc: Laura Abbott <[email protected]> Cc: Android Kernel Team <[email protected]> Alistair Strachan (1): staging: sync: Fix a race condition between release_obj and print_obj Colin Cross (1): staging: ion: Fix overflow and list bugs in system heap Greg Hackmann (1): staging: sw_sync: Add stubs for kernels without CONFIG_SW_SYNC John Stultz (1): staging: ion: Fix build warning Laura Abbott (1): staging: ion: Fix ION_IOC_FREE compat ioctl Prakash Kamliya (1): staging: sync: Signal pt before sync_timeline object gets destroyed Todd Poynor (1): staging: ashmem: Avoid deadlock between read and mmap calls drivers/staging/android/ashmem.c | 45 ++++++++++++++++----------- drivers/staging/android/ion/compat_ion.c | 26 +++++++++++++--- drivers/staging/android/ion/ion_priv.h | 1 + drivers/staging/android/ion/ion_system_heap.c | 6 +++- drivers/staging/android/sw_sync.h | 17 ++++++++++ drivers/staging/android/sync.c | 14 ++++----- 6 files changed, 78 insertions(+), 31 deletions(-) -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
