Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965081AbXA3D5X (ORCPT ); Mon, 29 Jan 2007 22:57:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965021AbXA3D5X (ORCPT ); Mon, 29 Jan 2007 22:57:23 -0500 Received: from rex.snapgear.com ([203.143.235.140]:43480 "EHLO cyberguard.com.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S965081AbXA3D5W (ORCPT ); Mon, 29 Jan 2007 22:57:22 -0500 X-Greylist: delayed 1236 seconds by postgrey-1.27 at vger.kernel.org; Mon, 29 Jan 2007 22:57:21 EST Message-ID: <45BEC21C.2000402@securecomputing.com> Date: Tue, 30 Jan 2007 13:57:16 +1000 From: Greg Ungerer User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Dave Jones , Greg Ungerer , Jes Sorensen , Theodore Tso , Sunil Naidu , linux-kernel@vger.kernel.org, dirk.hohndel@intel.com, alan@redhat.com, ksummit-2007-discuss@thunk.org, David Miller Subject: Re: [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit References: <20070123.095756.30177490.davem@davemloft.net> <20070125.125121.98861775.davem@davemloft.net> <8355959a0701251646t4b7db48cj862268aad52e8e24@mail.gmail.com> <20070126032849.GB5589@thunk.org> <8355959a0701260704x6aea8141s3d0581fa33c74cf2@mail.gmail.com> <20070126195024.GE14759@thunk.org> <45BE8BF9.6020204@sgi.com> <20070130030430.GA21772@redhat.com> <45BEBBF0.3050102@snapgear.com> <20070130034111.GB21772@redhat.com> In-Reply-To: <20070130034111.GB21772@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1671 Lines: 34 Dave Jones wrote: > On Tue, Jan 30, 2007 at 01:30:56PM +1000, Greg Ungerer wrote: > > > > Dave Jones wrote: > > > On Tue, Jan 30, 2007 at 01:06:17AM +0100, Jes Sorensen wrote: > > > > Then there is the issue of architectures, at least in my book KS should > > > > focus on the ones that are really live and not in maintenance mode. > > > > x86_64, x86_32, PPC, ia64, ARM seems to be the driving ones these days, > > > > m68k, Sparc32, and others, somewhat less so ..... > > > > > > Again, I don't recall us spending any time at all discussing m68k, or > > > sparc, whilst the others you mention were well represented. > > > > Well, others where represented, I was there looking after non-mmu m68k > > for example (and other general non-mmu stuff). There just wasn't much > > contentious stuff in that space that needed wider discussion. > > Right, other than during the CPU architects panel, I don't remember > any non x86/ia64/ppc stuff being brought up at all. Yep. IIRC the CPU architects panel was all x86/x86_64/ppc too wasn't it? ------------------------------------------------------------------------ Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com SnapGear -- a Secure Computing Company PHONE: +61 7 3435 2888 825 Stanley St, FAX: +61 7 3891 3630 Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com - 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/