Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758501Ab2FZIJq (ORCPT ); Tue, 26 Jun 2012 04:09:46 -0400 Received: from cpsmtpb-ews03.kpnxchange.com ([213.75.39.6]:2447 "EHLO cpsmtpb-ews03.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757100Ab2FZIJn (ORCPT ); Tue, 26 Jun 2012 04:09:43 -0400 Message-ID: <1340698181.2197.14.camel@x61.thuisdomein> Subject: Re: [PATCH] avr32: Remove unused asm/numnodes.h From: Paul Bolle To: Hans-Christian Egtvedt Cc: Haavard Skinnemoen , linux-kernel@vger.kernel.org Date: Tue, 26 Jun 2012 10:09:41 +0200 In-Reply-To: <20120626073255.GB7866@samfundet.no> References: <1339174815.30984.8.camel@x61.thuisdomein> <20120626073255.GB7866@samfundet.no> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3 (3.2.3-3.fc16) Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-OriginalArrivalTime: 26 Jun 2012 08:09:42.0031 (UTC) FILETIME=[0A2761F0:01CD5373] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 29 Hans-Christian, On Tue, 2012-06-26 at 09:32 +0200, Hans-Christian Egtvedt wrote: > Around Fri 08 Jun 2012 19:00:15 +0200 or thereabout, Paul Bolle wrote: > > This is handled with config options now. > > Yes, but AVR32 doesn't have those bits in arch/avr32/Kconfig, Correct. Currently only 11 of 26 architectures set the Kconfig symbol NODES_SHIFT. avr32 is not one of those 11. > hence removing > the NODES_SHIFT definition will reduce it to 0 in include/Linux/numa.h. I > suspect it is already done... Sure, NODES_SHIFT will be defined as 0 in numa.h for avr32, because CONFIG_NODES_SHIFT will never be defined for avr32. Or do you mean that some file is actually using avr32's asm/numnodes.h? How does that work? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/