[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1387256873-21350-1-git-send-email-john.stultz@linaro.org>
Date: Mon, 16 Dec 2013 21:07:50 -0800
From: John Stultz <john.stultz@...aro.org>
To: LKML <linux-kernel@...r.kernel.org>
Cc: John Stultz <john.stultz@...aro.org>,
Colin Cross <ccross@...roid.com>,
Android Kernel Team <kernel-team@...roid.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: [PATCH 0/3] ION fixups for staging-next (v2)
Since the ION patchset landed in staging-next, there have
been a few build issue reports, and this patchset tries
to address them.
Dropped the RFC, as I think the first two are good to go, but
I'd still like to get acks from Colin or someone else on the
Android team on all of these before merging these, as some bits
were a bit more complex then I'd like.
Changes in v2:
o Fixed up style issue Greg caught
o Reworked second patch to simplify error path and just return
null if kmalloc fails
o Per Colin's suggestion, reworked third patch to use spinlocks.
This ended up being a bit more complicated to get right, and
I'd appreciate very close review, but it seems to be working
ok in testing on both ARM and x86_64 w/o triggering any lockdep
or other warnings.
I'd appreciate any thoughts or comments!
thanks
-john
Cc: Colin Cross <ccross@...roid.com>
Cc: Android Kernel Team <kernel-team@...roid.com>
Cc: Greg KH <gregkh@...uxfoundation.org>
John Stultz (3):
staging: ion: Add HAVE_MEMBLOCK config dependency
staging: ion: Fix possible null pointer dereference
staging: ion: Avoid using rt_mutexes directly.
drivers/staging/android/ion/Kconfig | 1 +
drivers/staging/android/ion/ion_heap.c | 31 ++++++++++++++++-----------
drivers/staging/android/ion/ion_priv.h | 2 +-
drivers/staging/android/ion/ion_system_heap.c | 7 +++++-
4 files changed, 27 insertions(+), 14 deletions(-)
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists