mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
	Colin Cross <ccross@android.com>,
	Android Kernel Team <kernel-team@android.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: [PATCH 0/3] ION fixups for staging-next (v2)
Date: Mon, 16 Dec 2013 21:07:50 -0800	[thread overview]
Message-ID: <1387256873-21350-1-git-send-email-john.stultz@linaro.org> (raw)

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@android.com>
Cc: Android Kernel Team <kernel-team@android.com>
Cc: Greg KH <gregkh@linuxfoundation.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


             reply	other threads:[~2013-12-17  5:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  5:07 John Stultz [this message]
2013-12-17  5:07 ` [PATCH 1/3] staging: ion: Add HAVE_MEMBLOCK config dependency John Stultz
2013-12-17  7:25   ` Colin Cross
2013-12-17  5:07 ` [PATCH 2/3] staging: ion: Fix possible null pointer dereference John Stultz
2013-12-17  7:26   ` Colin Cross
2013-12-17  5:07 ` [PATCH 3/3] staging: ion: Avoid using rt_mutexes directly John Stultz
2013-12-17  7:25   ` Colin Cross
2013-12-18  1:04     ` [PATCH v3] " John Stultz
2013-12-18  1:07       ` Colin Cross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1387256873-21350-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=ccross@android.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®