From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 86B7CB7DDE for ; Sun, 13 Jun 2010 18:58:00 +1000 (EST) Subject: Re: Request review of device tree documentation From: Benjamin Herrenschmidt To: Mitch Bradley In-Reply-To: <4C147EA5.3060500@firmworks.com> References: <33BD8E86-9397-432A-97BF-F154812C157B@digitaldans.com> <4C13430B.5000907@firmworks.com> <1276339529.1962.184.camel@pasglop> <1276339684.1962.186.camel@pasglop> <4C13B618.1030006@firmworks.com> <1276383132.1962.195.camel@pasglop> <4C146F18.9030008@firmworks.com> <1276408773.1962.574.camel@pasglop> <4C147EA5.3060500@firmworks.com> Content-Type: text/plain; charset="UTF-8" Date: Sun, 13 Jun 2010 18:57:40 +1000 Message-ID: <1276419460.1962.759.camel@pasglop> Mime-Version: 1.0 Cc: microblaze-uclinux@itee.uq.edu.au, devicetree-discuss , linuxppc-dev , Olof Johansson , Dan Malek , Jeremy Kerr List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 2010-06-12 at 20:45 -1000, Mitch Bradley wrote: > > BTW. I notice no ARM list is CCed on this discussion ... maybe we > should > > fix that ? > > > > Sounds like a good idea. Do you know which list(s) would be good > candidates? Forgot to reply to that one ... I'd say linux-arm-kernel@lists.infradead.org For now. If the discussion starts taking too much bandwidth, it might be worth creating a special list for ARM device-tree / OF. Cheers, Ben. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Request review of device tree documentation Date: Sun, 13 Jun 2010 18:57:40 +1000 Message-ID: <1276419460.1962.759.camel@pasglop> References: <33BD8E86-9397-432A-97BF-F154812C157B@digitaldans.com> <4C13430B.5000907@firmworks.com> <1276339529.1962.184.camel@pasglop> <1276339684.1962.186.camel@pasglop> <4C13B618.1030006@firmworks.com> <1276383132.1962.195.camel@pasglop> <4C146F18.9030008@firmworks.com> <1276408773.1962.574.camel@pasglop> <4C147EA5.3060500@firmworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C147EA5.3060500-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Mitch Bradley Cc: microblaze-uclinux-rVRm/Wmeqae7NGdpmJTKYQ@public.gmane.org, devicetree-discuss , linuxppc-dev , Dan Malek , Jeremy Kerr List-Id: devicetree@vger.kernel.org On Sat, 2010-06-12 at 20:45 -1000, Mitch Bradley wrote: > > BTW. I notice no ARM list is CCed on this discussion ... maybe we > should > > fix that ? > > > > Sounds like a good idea. Do you know which list(s) would be good > candidates? Forgot to reply to that one ... I'd say linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org For now. If the discussion starts taking too much bandwidth, it might be worth creating a special list for ARM device-tree / OF. Cheers, Ben.