From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752646AbaJTSul (ORCPT ); Mon, 20 Oct 2014 14:50:41 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:56097 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751102AbaJTSui (ORCPT ); Mon, 20 Oct 2014 14:50:38 -0400 Date: Tue, 21 Oct 2014 02:49:32 +0800 From: Greg Kroah-Hartman To: Sudeep Holla Cc: LKML , Heiko Carstens , Lorenzo Pieralisi Subject: Re: [PATCH v5 00/11] drivers: cacheinfo support Message-ID: <20141020184932.GA25398@kroah.com> References: <1412084912-2767-1-git-send-email-sudeep.holla@arm.com> <5445587B.8090203@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5445587B.8090203@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 20, 2014 at 07:46:19PM +0100, Sudeep Holla wrote: > Hi Greg, > > On 30/09/14 14:48, Sudeep Holla wrote: > >This series adds a generic cacheinfo support similar to topology. The > >implementation is based on x86 cacheinfo support. Currently x86, powerpc, > >ia64 and s390 have their own implementations. While adding similar support > >to ARM and ARM64, here is the attempt to make it generic quite similar to > >topology info support. It also adds the missing ABI documentation for > >the cacheinfo sysfs which is already being used. > > > >It moves all the existing different implementations on x86, ia64, powerpc > >and s390 to use the generic cacheinfo infrastructure introduced here. > >These changes on non-ARM platforms are only compile tested and tested on x86. > > > >This series also adds support for ARM and ARM64 architectures based on > >the generic support. > > > >The code can be fetched from: > > git://linux-arm.org/linux-skn cacheinfo > > > > I am hoping to target this for v3.19 if possible, it would be good if > you can review and provide feedback. 3.18-rc1 just came out a few _hours_ ago, and now we can start worrying about what goes into 3.19. I have 1257 emails in my "to-review" queue for 3.19, please give me a chance to catch up in a few weeks to get to this code. thanks, greg k-h