From: Tomer Samara <tomersamara98@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "Sumit Semwal" <sumit.semwal@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <christian@brauner.io>,
"Hridya Valsaraju" <hridya@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
devel@driverdev.osuosl.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] *** SUBJECT HERE ***
Date: Tue, 18 Aug 2020 12:17:08 +0300 [thread overview]
Message-ID: <cover.1597742228.git.tomersamara98@gmail.com> (raw)
*** BLURB HERE ***
Tomer Samara (4):
staging: android: Replace BUG_ON with WARN_ON
staging: android: Add error handling to ion_page_pool_shrink
staging: android: Convert BUG to WARN
staging: android: Add error handling to order_to_index callers
drivers/staging/android/ion/ion_page_pool.c | 14 ++++++++++----
drivers/staging/android/ion/ion_system_heap.c | 16 +++++++++++++---
2 files changed, 23 insertions(+), 7 deletions(-)
--
2.25.1
/tmp/0001-staging-android-Replace-BUG_ON-with-WARN_ON.patch
/tmp/0002-staging-android-Add-error-handling-to-ion_page_pool_.patch
/tmp/0003-staging-android-Convert-BUG-to-WARN.patch
/tmp/0004-staging-android-Add-error-handling-to-order_to_index.patch
next reply other threads:[~2020-08-18 9:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 9:17 Tomer Samara [this message]
2020-08-18 9:50 ` [PATCH 0/4] *** SUBJECT HERE *** Greg Kroah-Hartman
2020-08-18 9:52 ` Tomer Samara
-- strict thread matches above, loose matches on Subject: below --
2025-12-12 3:13 Xiaoshun Xu
2025-12-12 11:30 ` Xiaoshun Xu (徐晓顺)
2020-08-18 8:52 Tomer Samara
2020-08-18 8:48 Tomer Samara
2020-08-18 8:47 Tomer Samara
2014-08-20 4:30 Valentina Manea
2014-08-25 17:43 ` Greg KH
2013-11-19 16:03 Charles Keepax
2013-11-19 16:03 Charles Keepax
2011-02-09 9:51 Tobias Klauser
2011-02-09 9:53 ` Tobias Klauser
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=cover.1597742228.git.tomersamara98@gmail.com \
--to=tomersamara98@gmail.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=sumit.semwal@linaro.org \
--cc=surenb@google.com \
--cc=tkjos@android.com \
/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;
as well as URLs for NNTP newsgroup(s).