From: Greg KH <gregkh@linuxfoundation.org>
To: Laura Abbott <labbott@redhat.com>
Cc: "Benjamin Gaignard" <benjamin.gaignard@linaro.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
"Mark Brown" <broonie@kernel.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
driverdevel <devel@driverdev.osuosl.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v6 2/2] staging: ion: create one device entry per heap
Date: Wed, 6 Dec 2017 07:28:22 +0100 [thread overview]
Message-ID: <20171206062822.GB20995@kroah.com> (raw)
In-Reply-To: <65ef83b2-db3e-eaf6-129f-40e156400624@redhat.com>
On Tue, Dec 05, 2017 at 03:01:42PM -0800, Laura Abbott wrote:
> On 12/02/2017 07:53 AM, Greg KH wrote:
> > > This is one of the item in the TODO list before been able to unstage ION
> > > which is my real need.
> > Why does it matter where in the tree this code is? Don't go adding new
> > things to it that are not needed. Who needs this? What userspace code
> > wants this type of multiple ion devices?
> >
>
> Requirements came in from several places to split /dev/ion -> /dev/ion0
> and /dev/ion1 so that security policy (i.e. selinux) could be used to
> protect access to certain heaps. I wanted the ABI to be settled before
> trying to move out of staging, hence the line in the TODO list about
> doing the split.
Ok, but we should have some way of testing it works, right? :)
next prev parent reply other threads:[~2017-12-06 6:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 15:59 [PATCH v6 0/2] staging: ion: get one device " Benjamin Gaignard
2017-11-06 15:59 ` [PATCH v6 1/2] staging: ion: reorder include Benjamin Gaignard
2017-11-09 21:02 ` Laura Abbott
2017-11-28 13:20 ` Greg KH
2017-11-28 13:34 ` Benjamin Gaignard
2017-11-28 13:40 ` Greg KH
2017-11-06 15:59 ` [PATCH v6 2/2] staging: ion: create one device entry per heap Benjamin Gaignard
2017-11-09 21:17 ` Laura Abbott
2017-11-27 10:46 ` Benjamin Gaignard
2017-11-27 11:43 ` Greg Kroah-Hartman
2017-11-27 16:12 ` Daniel Vetter
2017-11-27 16:30 ` Mark Brown
2017-11-28 13:32 ` Greg KH
2017-11-28 16:26 ` Mark Brown
2017-11-28 17:08 ` Greg KH
2017-11-28 17:12 ` Mark Brown
2017-11-28 17:28 ` Greg KH
2017-11-28 17:37 ` Mark Brown
2017-11-28 18:00 ` Greg KH
2017-11-29 14:00 ` Benjamin Gaignard
2017-12-02 15:53 ` Greg KH
2017-12-05 23:01 ` Laura Abbott
2017-12-06 6:28 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-23 15:55 [PATCH v6 0/2] staging: ion: get one device " Benjamin Gaignard
2017-10-23 15:55 ` [PATCH v6 2/2] staging: ion: create one device entry " Benjamin Gaignard
2017-10-24 16:14 ` Jordan Crouse
2017-10-31 19:03 ` Laura Abbott
2017-10-31 19:11 ` Mark Brown
2017-10-31 19:45 ` Laura Abbott
2017-11-02 10:44 ` Greg KH
2017-11-02 11:10 ` Mark Brown
2017-11-06 14:42 ` Benjamin Gaignard
2017-11-06 14:46 ` Greg KH
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=20171206062822.GB20995@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=labbott@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=sumit.semwal@linaro.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
Powered by JetHome