From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932294AbcBAV2s (ORCPT ); Mon, 1 Feb 2016 16:28:48 -0500 Received: from mail-yk0-f174.google.com ([209.85.160.174]:33463 "EHLO mail-yk0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751722AbcBAV2r (ORCPT ); Mon, 1 Feb 2016 16:28:47 -0500 MIME-Version: 1.0 In-Reply-To: <56AFC9C8.2090904@redhat.com> References: <1454134058-16466-1-git-send-email-john.stultz@linaro.org> <56AFC9C8.2090904@redhat.com> Date: Mon, 1 Feb 2016 13:28:46 -0800 Message-ID: Subject: Re: [PATCH 0/9] staging: Updates from the Android tree From: John Stultz To: Laura Abbott Cc: lkml , Android Kernel Team , Greg KH , Sumit Semwal Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 1, 2016 at 1:10 PM, Laura Abbott wrote: > On 01/29/2016 10:07 PM, John Stultz wrote: >> >> In reviewing the experimental/android-4.4 tree from AOSP, I >> realized there were a handful of patches to code in the >> staging/android directory. >> >> So I wanted to send these along for review, so if there were >> no objections they could be queued for 4.6. >> >> Let me know if there is any comments or feedback > > > I'm not thrilled about the patches for the cache policy. It certainly > fixes the problem for x86 but I'd rather see a more unified caching > approach which would also abstract some of the cache flushing. Fair enough. Though I worry that keeping them out of mainline's staging makes it more difficult to get a proper solution upstream, since it creates more out of tree variants, which users may have subtle dependencies on. But that's more of a general worry then a specific concern here. thanks -john