From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754511AbaGKPox (ORCPT ); Fri, 11 Jul 2014 11:44:53 -0400 Received: from kirsty.vergenet.net ([202.4.237.240]:41417 "EHLO kirsty.vergenet.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753503AbaGKPow (ORCPT ); Fri, 11 Jul 2014 11:44:52 -0400 Date: Fri, 11 Jul 2014 17:44:43 +0200 From: Simon Horman To: Nick Krause Cc: Magnus Damm , Russell King - ARM Linux , linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "linux-kernel@vger.kernel.org" Subject: Re: mach-shmobile: FIXME message in file pm-sh732.c Message-ID: <20140711154443.GD1777@verge.net.au> References: <20140711093450.GA26660@verge.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organisation: Horms Solutions Ltd. 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 Fri, Jul 11, 2014 at 11:24:12AM -0400, Nick Krause wrote: > On Fri, Jul 11, 2014 at 5:34 AM, Simon Horman wrote: > > On Fri, Jul 04, 2014 at 12:34:58AM -0400, Nick Krause wrote: > >> While searching for FIX ME messages when using cscope on the latest kernels I > >> get a message on 68 of this file and was wondering what I need to define SMFRAM > >> as in order for it to point to things needed to support this portion > >> of the hardware. > > > > Hi Nick, > > > > while I don't have a technical answer to your question I do believe > > that the code in question will be removed in the not too distant future > > along with support for the sh7372 SoC. > > Why are we removing support for this SoC? Is there any reason? Because it is rather old hardware which is most likely not used against mainline by anyone other than those maintaining the code and moving it over to use multiplatform, CCF, and the like appears to be more work thank it is worth.