From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mundt Subject: Re: [PATCH for 2.6.28 stable] m68knommu: fix m68knommu defconfig can't build Date: Mon, 12 Jan 2009 19:44:47 +0900 Message-ID: <20090112104447.GG28564@linux-sh.org> References: <20081230193943.1281.KOSAKI.MOTOHIRO@jp.fujitsu.com> <48E9AE16.2000002@snapgear.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <48E9AE16.2000002@snapgear.com> Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Greg Ungerer Cc: KOSAKI Motohiro , "David S. Miller" , Geert Uytterhoeven , Roman Zippel , Greg Ungerer , linux-m68k@lists.linux-m68k.org, stable@kernel.org, LKML On Mon, Oct 06, 2008 at 04:20:06PM +1000, Greg Ungerer wrote: > Hi Kosako, > > KOSAKI Motohiro wrote: > >I guess nobody don't test m68knommu at all last three month. > >Do we still need to maintain this architecture? > > Yes, we do. > Any effort to get m68knommu folded in to m68k proper? This might help with some of your bitrot issues.. And likely less work to do in supporting those m68knommu parts that ship with MMUs ;-) m68knommu is the only one of the mmu/nommu variants left that ships in its own architecture directory rather than being folded in to its parent. It would be good to get rid of it one of these days. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754486AbZALKrg (ORCPT ); Mon, 12 Jan 2009 05:47:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752165AbZALKr0 (ORCPT ); Mon, 12 Jan 2009 05:47:26 -0500 Received: from mta23.gyao.ne.jp ([125.63.38.249]:64590 "EHLO mx.gate01.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751786AbZALKrZ (ORCPT ); Mon, 12 Jan 2009 05:47:25 -0500 Date: Mon, 12 Jan 2009 19:44:47 +0900 From: Paul Mundt To: Greg Ungerer Cc: KOSAKI Motohiro , "David S. Miller" , Geert Uytterhoeven , Roman Zippel , Greg Ungerer , linux-m68k@vger.kernel.org, stable@kernel.org, LKML Subject: Re: [PATCH for 2.6.28 stable] m68knommu: fix m68knommu defconfig can't build Message-ID: <20090112104447.GG28564@linux-sh.org> Mail-Followup-To: Paul Mundt , Greg Ungerer , KOSAKI Motohiro , "David S. Miller" , Geert Uytterhoeven , Roman Zippel , Greg Ungerer , linux-m68k@lists.linux-m68k.org, stable@kernel.org, LKML References: <20081230193943.1281.KOSAKI.MOTOHIRO@jp.fujitsu.com> <48E9AE16.2000002@snapgear.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48E9AE16.2000002@snapgear.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 06, 2008 at 04:20:06PM +1000, Greg Ungerer wrote: > Hi Kosako, > > KOSAKI Motohiro wrote: > >I guess nobody don't test m68knommu at all last three month. > >Do we still need to maintain this architecture? > > Yes, we do. > Any effort to get m68knommu folded in to m68k proper? This might help with some of your bitrot issues.. And likely less work to do in supporting those m68knommu parts that ship with MMUs ;-) m68knommu is the only one of the mmu/nommu variants left that ships in its own architecture directory rather than being folded in to its parent. It would be good to get rid of it one of these days.