Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751864AbXAaAKE (ORCPT ); Tue, 30 Jan 2007 19:10:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751960AbXAaAKE (ORCPT ); Tue, 30 Jan 2007 19:10:04 -0500 Received: from rex.snapgear.com ([203.143.235.140]:49223 "EHLO cyberguard.com.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751864AbXAaAKD (ORCPT ); Tue, 30 Jan 2007 19:10:03 -0500 Message-ID: <45BFDE54.1040805@securecomputing.com> Date: Wed, 31 Jan 2007 10:09:56 +1000 From: Greg Ungerer User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Jes Sorensen Cc: David Miller , linux-kernel@vger.kernel.org, alan@redhat.com, ksummit-2007-discuss@thunk.org, Sunil Naidu 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> <45BED029.8080100@sgi.com> In-Reply-To: <45BED029.8080100@sgi.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: 1303 Lines: 36 Jes Sorensen wrote: > Greg Ungerer wrote: >> Dave Jones wrote: >>> 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. > > Which is good, provided that non-mmu work is actively driving some of > the decisions in mainline. Given that I don't follow the non-mmu work > at all, I don't have a feel for whether that is the case, but I could > imagine that it would have some impact that needs to be taken into > account at times. Exactly. > My worry is for spending time and slots on things / > people dealing with classic architectures which are no longer being > manufactured and are only being maintained in catch-up mode. Agreed, but I haven't seen that in the past. The CPU panel at least has always covered current (and future) hardware. Regards Greg - 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/