lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 16 Oct 2020 10:29:45 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Laura Abbott <laura@...bott.name>
Cc:     sumit.semwal@...aro.org, john.stultz@...aro.org,
        devel@...verdev.osuosl.org, linaro-mm-sig@...ts.linaro.org,
        Shuah Khan <shuah@...nel.org>, Todd Kjos <tkjos@...roid.com>,
        Martijn Coenen <maco@...roid.com>,
        linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
        Suren Baghdasaryan <surenb@...gle.com>,
        Christoph Hellwig <hch@...radead.org>,
        Joel Fernandes <joel@...lfernandes.org>,
        Arve Hjønnevåg <arve@...roid.com>,
        Hridya Valsaraju <hridya@...gle.com>, kernel-team@...roid.com,
        Christian König <christian.koenig@....com>,
        Christian Brauner <christian@...uner.io>
Subject: Re: [PATCH] staging: ion: remove from the tree

On Thu, Aug 27, 2020 at 09:31:27AM -0400, Laura Abbott wrote:
> On 8/27/20 8:36 AM, Greg Kroah-Hartman wrote:
> > The ION android code has long been marked to be removed, now that we
> > dma-buf support merged into the real part of the kernel.
> > 
> > It was thought that we could wait to remove the ion kernel at a later
> > time, but as the out-of-tree Android fork of the ion code has diverged
> > quite a bit, and any Android device using the ion interface uses that
> > forked version and not this in-tree version, the in-tree copy of the
> > code is abandonded and not used by anyone.
> > 
> > Combine this abandoned codebase with the need to make changes to it in
> > order to keep the kernel building properly, which then causes merge
> > issues when merging those changes into the out-of-tree Android code, and
> > you end up with two different groups of people (the in-kernel-tree
> > developers, and the Android kernel developers) who are both annoyed at
> > the current situation.  Because of this problem, just drop the in-kernel
> > copy of the ion code now, as it's not used, and is only causing problems
> > for everyone involved.
> > 
> > Cc: "Arve Hjønnevåg" <arve@...roid.com>
> > Cc: "Christian König" <christian.koenig@....com>
> > Cc: Christian Brauner <christian@...uner.io>
> > Cc: Christoph Hellwig <hch@...radead.org>
> > Cc: Hridya Valsaraju <hridya@...gle.com>
> > Cc: Joel Fernandes <joel@...lfernandes.org>
> > Cc: John Stultz <john.stultz@...aro.org>
> > Cc: Laura Abbott <laura@...bott.name>
> > Cc: Martijn Coenen <maco@...roid.com>
> > Cc: Shuah Khan <shuah@...nel.org>
> > Cc: Sumit Semwal <sumit.semwal@...aro.org>
> > Cc: Suren Baghdasaryan <surenb@...gle.com>
> > Cc: Todd Kjos <tkjos@...roid.com>
> > Cc: devel@...verdev.osuosl.org
> > Cc: dri-devel@...ts.freedesktop.org
> > Cc: linaro-mm-sig@...ts.linaro.org
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
> We discussed this at the Android MC on Monday and the plan was to
> remove it after the next LTS release.

As 5.10 will be the next LTS release, I have now merged it to my
"testing" branch to go into 5.11-rc1.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ