From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: Representing Embedded Architectures at the Kernel Summit Date: Tue, 02 Jun 2009 12:42:57 -0500 Message-ID: <1243964577.4229.49.camel@mulgrave.int.hansenpartnership.com> References: <1243956140.4229.25.camel@mulgrave.int.hansenpartnership.com> <20090602172941.GL3095@hansolo.jdub.homelinux.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from bedivere.hansenpartnership.com ([66.63.167.143]:33750 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758224AbZFBRnA (ORCPT ); Tue, 2 Jun 2009 13:43:00 -0400 In-Reply-To: <20090602172941.GL3095@hansolo.jdub.homelinux.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Josh Boyer Cc: ksummit-2009-discuss@lists.linux-foundation.org, linux-arch@vger.kernel.org, linux-embedded@vger.kernel.org On Tue, 2009-06-02 at 13:29 -0400, Josh Boyer wrote: > Which leads me to suggest that it is at least worth having someone with an > embedded focus at KS to simply keep an eye out for impacts of generic changes. > "Feature parity" is something I often deal with in trying to keep ppc4xx up to > speed with the rest of the archs in the kernel. We're fine with this, if that's how the embedded guys would like to do it ... how do you want to nominate the "someone with an embedded focus"? We chose the topic driven approach because that's the one it's easiest for the Kernel Summit Programme Committee to look at and make attendance decisions based upon. However, if all the embedded people want to choose their own representatives, that's fine by us too ... as long as you can devise a fair process. James