From: Christoph Hellwig <hch@infradead.org>
To: Tomer Samara <tomersamara98@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arve Hj?nnev?g <arve@android.com>,
Riley Andrews <riandrews@android.com>,
Laura Abbott <labbott@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] staging: android: Remove BUG/BUG_ON from ion
Date: Tue, 25 Aug 2020 07:47:29 +0100 [thread overview]
Message-ID: <20200825064729.GA30014@infradead.org> (raw)
In-Reply-To: <cover.1598023523.git.tomersamara98@gmail.com>
On Fri, Aug 21, 2020 at 06:27:04PM +0300, Tomer Samara wrote:
> Remove BUG/BUG_ON from androind/ion
Please just remove ion. It has been rejected and we have developed
proper kernel subsystens to replace it. Don't waste your time on it.
next prev parent reply other threads:[~2020-08-25 6:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 15:27 [PATCH v4 0/2] staging: android: Remove BUG/BUG_ON from ion Tomer Samara
2020-08-21 15:27 ` [PATCH v4 1/2] staging: android: Remove BUG_ON from ion_page_pool.c Tomer Samara
2020-08-24 11:22 ` Dan Carpenter
2020-08-21 15:28 ` [PATCH v4 2/2] staging: android: Remove BUG from ion_system_heap.c Tomer Samara
2020-08-21 16:25 ` Randy Dunlap
2020-08-22 9:34 ` Tomer Samara
2020-08-22 14:22 ` Randy Dunlap
2020-08-24 11:24 ` Dan Carpenter
2020-08-24 11:27 ` Dan Carpenter
2020-08-24 11:43 ` Dan Carpenter
2020-08-25 6:47 ` Christoph Hellwig [this message]
2020-08-25 6:52 ` [PATCH v4 0/2] staging: android: Remove BUG/BUG_ON from ion Greg Kroah-Hartman
2020-08-27 7:16 ` Christoph Hellwig
2020-08-27 12:15 ` Greg Kroah-Hartman
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=20200825064729.GA30014@infradead.org \
--to=hch@infradead.org \
--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=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=riandrews@android.com \
--cc=sumit.semwal@linaro.org \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tomersamara98@gmail.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