From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id D12DADE137 for ; Thu, 23 Apr 2009 07:34:53 +1000 (EST) Message-ID: <49EF8D42.7010104@freescale.com> Date: Wed, 22 Apr 2009 16:33:54 -0500 From: Timur Tabi MIME-Version: 1.0 To: Kumar Gala Subject: Re: removing get_immrbase()?? References: <49EF7B11.2000006@freescale.com> <49EF7B1C.2080105@freescale.com> <282847E1-AE1A-44EF-9D18-AF2884105FA5@kernel.crashing.org> In-Reply-To: <282847E1-AE1A-44EF-9D18-AF2884105FA5@kernel.crashing.org> Content-Type: text/plain; charset=ISO-8859-1 Cc: Scott Wood , Linuxppc-dev Development List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Kumar Gala wrote: > I disagree. If you update your kernel you should update your device > tree (thus we have .dts in the kernel tree and not somewhere else). Is this a new policy? I was under the impression that supporting older device trees, if not too inconvenient, is desirable. I've nack'd patches before that broke backwards compatibility unnecessarily. -- Timur Tabi Linux kernel developer at Freescale