From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751082AbdCNMIg (ORCPT ); Tue, 14 Mar 2017 08:08:36 -0400 Received: from mail-qt0-f195.google.com ([209.85.216.195]:35708 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750805AbdCNMIf (ORCPT ); Tue, 14 Mar 2017 08:08:35 -0400 MIME-Version: 1.0 In-Reply-To: <3e06a16339303016b2c57b350a15afeaa7ba7813.1487702890.git.shorne@gmail.com> References: <3e06a16339303016b2c57b350a15afeaa7ba7813.1487702890.git.shorne@gmail.com> From: Sudeep Holla Date: Tue, 14 Mar 2017 12:08:33 +0000 X-Google-Sender-Auth: KZfjyZYbDgO5nMvIJU73lnmJrPc Message-ID: Subject: Re: [PATCH v3 02/25] openrisc: add cache way information to cpuinfo To: Stafford Horne Cc: Jonas Bonn , Stefan Kristiansson , linux@roeck-us.net, openrisc@lists.librecores.org, open list , Olof Kindgren , Rob Herring 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 Tue, Feb 21, 2017 at 7:11 PM, Stafford Horne wrote: > From: Stefan Kristiansson > > Motivation for this is to be able to print the way information > properly in print_cpuinfo(), instead of hardcoding it to one. > Any particular reason not to use generic cacheinfo sysfs infrastructure ? -- Regards, Sudeep From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sudeep Holla Date: Tue, 14 Mar 2017 12:08:33 +0000 Subject: [OpenRISC] [PATCH v3 02/25] openrisc: add cache way information to cpuinfo In-Reply-To: <3e06a16339303016b2c57b350a15afeaa7ba7813.1487702890.git.shorne@gmail.com> References: <3e06a16339303016b2c57b350a15afeaa7ba7813.1487702890.git.shorne@gmail.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: openrisc@lists.librecores.org On Tue, Feb 21, 2017 at 7:11 PM, Stafford Horne wrote: > From: Stefan Kristiansson > > Motivation for this is to be able to print the way information > properly in print_cpuinfo(), instead of hardcoding it to one. > Any particular reason not to use generic cacheinfo sysfs infrastructure ? -- Regards, Sudeep