[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45BFDE54.1040805@securecomputing.com>
Date: Wed, 31 Jan 2007 10:09:56 +1000
From: Greg Ungerer <greg_ungerer@...urecomputing.com>
To: Jes Sorensen <jes@....com>
Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
alan@...hat.com, ksummit-2007-discuss@...nk.org,
Sunil Naidu <akula2.shark@...il.com>
Subject: Re: [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux
Kernel Summit
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists