From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 13/14] staging: android: ion: Do not sync CPU cache on map/unmap Date: Sat, 19 Jan 2019 02:11:18 -0800 Message-ID: <20190119101118.GA2127@infradead.org> References: <20190111180523.27862-14-afd@ti.com> <79eb70f6-00b0-2939-5ec9-65e196ab4987@ti.com> <99ca0b08-02bd-64fd-d43c-c330f0d11639@ti.com> <7620534f-b749-76f9-0f53-f73e3f12e9a9@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Laura Abbott Cc: "Andrew F. Davis" , Liam Mark , Sumit Semwal , Greg Kroah-Hartman , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, dri-devel List-Id: dri-devel@lists.freedesktop.org On Fri, Jan 18, 2019 at 12:31:34PM -0800, Laura Abbott wrote: > I thought about doing that, the problem is it becomes an ABI break for > existing users which I really didn't want to do again. If it > ends up being the last thing we do before moving out of staging, > I'd consider doing it. This is staging code, so any existing users by defintion do not matter. Let's not drag Linux development down over this.