From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from service87.mimecast.com (service87.mimecast.com [91.220.42.44]) by ozlabs.org (Postfix) with ESMTP id 9FD922C0142 for ; Fri, 10 Jan 2014 06:07:44 +1100 (EST) Message-ID: <52CEF383.3070405@arm.com> Date: Thu, 09 Jan 2014 19:07:47 +0000 From: Sudeep Holla MIME-Version: 1.0 To: Greg Kroah-Hartman Subject: Re: [PATCH RFC 1/3] drivers: base: support cpu cache information interface to userspace via sysfs References: <1389209168-17189-1-git-send-email-sudeep.holla@arm.com> <1389209168-17189-2-git-send-email-sudeep.holla@arm.com> <20140108202826.GF8417@kroah.com> In-Reply-To: <20140108202826.GF8417@kroah.com> Content-Type: text/plain; charset=WINDOWS-1252 Cc: "devicetree@vger.kernel.org" , Ashok Raj , Rob Herring , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Sudeep.Holla@arm.com, "linuxppc-dev@lists.ozlabs.org" , "linux-arm-kernel@lists.infradead.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 08/01/14 20:28, Greg Kroah-Hartman wrote: > On Wed, Jan 08, 2014 at 07:26:06PM +0000, Sudeep Holla wrote: >> From: Sudeep Holla >> +#define define_one_ro(_name) \ >> +static struct cache_attr _name =3D \ >> +=09__ATTR(_name, 0444, show_##_name, NULL) >=20 > In the future, we do have __ATTR_RO(), which should be used instead. > You should never use __ATTR() on it's own, if at all possible. I'm > sweeping the tree for all usages and fixing them slowly up over time. >=20 Understood, will fix it. Regards, Sudeep From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sudeep.Holla@arm.com (Sudeep Holla) Date: Thu, 09 Jan 2014 19:07:47 +0000 Subject: [PATCH RFC 1/3] drivers: base: support cpu cache information interface to userspace via sysfs In-Reply-To: <20140108202826.GF8417@kroah.com> References: <1389209168-17189-1-git-send-email-sudeep.holla@arm.com> <1389209168-17189-2-git-send-email-sudeep.holla@arm.com> <20140108202826.GF8417@kroah.com> Message-ID: <52CEF383.3070405@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 08/01/14 20:28, Greg Kroah-Hartman wrote: > On Wed, Jan 08, 2014 at 07:26:06PM +0000, Sudeep Holla wrote: >> From: Sudeep Holla >> +#define define_one_ro(_name) \ >> +static struct cache_attr _name = \ >> + __ATTR(_name, 0444, show_##_name, NULL) > > In the future, we do have __ATTR_RO(), which should be used instead. > You should never use __ATTR() on it's own, if at all possible. I'm > sweeping the tree for all usages and fixing them slowly up over time. > Understood, will fix it. Regards, Sudeep From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sudeep Holla Subject: Re: [PATCH RFC 1/3] drivers: base: support cpu cache information interface to userspace via sysfs Date: Thu, 09 Jan 2014 19:07:47 +0000 Message-ID: <52CEF383.3070405@arm.com> References: <1389209168-17189-1-git-send-email-sudeep.holla@arm.com> <1389209168-17189-2-git-send-email-sudeep.holla@arm.com> <20140108202826.GF8417@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <20140108202826.GF8417-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Greg Kroah-Hartman Cc: Sudeep.Holla-5wv7dgnIgG8@public.gmane.org, "x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , "linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Ashok Raj , Benjamin Herrenschmidt , Rob Herring List-Id: devicetree@vger.kernel.org On 08/01/14 20:28, Greg Kroah-Hartman wrote: > On Wed, Jan 08, 2014 at 07:26:06PM +0000, Sudeep Holla wrote: >> From: Sudeep Holla >> +#define define_one_ro(_name) \ >> +static struct cache_attr _name = \ >> + __ATTR(_name, 0444, show_##_name, NULL) > > In the future, we do have __ATTR_RO(), which should be used instead. > You should never use __ATTR() on it's own, if at all possible. I'm > sweeping the tree for all usages and fixing them slowly up over time. > Understood, will fix it. Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756598AbaAITIE (ORCPT ); Thu, 9 Jan 2014 14:08:04 -0500 Received: from service87.mimecast.com ([91.220.42.44]:34576 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756345AbaAITHo convert rfc822-to-8bit (ORCPT ); Thu, 9 Jan 2014 14:07:44 -0500 Message-ID: <52CEF383.3070405@arm.com> Date: Thu, 09 Jan 2014 19:07:47 +0000 From: Sudeep Holla User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Greg Kroah-Hartman CC: Sudeep.Holla@arm.com, "x86@kernel.org" , "linuxppc-dev@lists.ozlabs.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Ashok Raj , Benjamin Herrenschmidt , Rob Herring Subject: Re: [PATCH RFC 1/3] drivers: base: support cpu cache information interface to userspace via sysfs References: <1389209168-17189-1-git-send-email-sudeep.holla@arm.com> <1389209168-17189-2-git-send-email-sudeep.holla@arm.com> <20140108202826.GF8417@kroah.com> In-Reply-To: <20140108202826.GF8417@kroah.com> X-OriginalArrivalTime: 09 Jan 2014 19:07:39.0965 (UTC) FILETIME=[10FD8ED0:01CF0D6E] X-MC-Unique: 114010919074200301 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/01/14 20:28, Greg Kroah-Hartman wrote: > On Wed, Jan 08, 2014 at 07:26:06PM +0000, Sudeep Holla wrote: >> From: Sudeep Holla >> +#define define_one_ro(_name) \ >> +static struct cache_attr _name = \ >> + __ATTR(_name, 0444, show_##_name, NULL) > > In the future, we do have __ATTR_RO(), which should be used instead. > You should never use __ATTR() on it's own, if at all possible. I'm > sweeping the tree for all usages and fixing them slowly up over time. > Understood, will fix it. Regards, Sudeep