From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751430AbdARXkb (ORCPT ); Wed, 18 Jan 2017 18:40:31 -0500 Received: from mail-pg0-f54.google.com ([74.125.83.54]:34265 "EHLO mail-pg0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751253AbdARXk1 (ORCPT ); Wed, 18 Jan 2017 18:40:27 -0500 From: Kevin Hilman To: Andreas =?utf-8?Q?F=C3=A4rber?= Cc: Neil Armstrong , linux-amlogic@lists.infradead.org, Carlo Caione , Mark Rutland , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro Organization: BayLibre References: <20170117030611.23827-2-afaerber@suse.de> <20170117225459.4438-1-afaerber@suse.de> <20170117225459.4438-2-afaerber@suse.de> <819ac0c0-92b7-bac7-dcfc-a56c34a6bf62@baylibre.com> <9439ba55-c56c-71bf-00a5-870e2f4dd07b@suse.de> Date: Wed, 18 Jan 2017 15:38:57 -0800 In-Reply-To: <9439ba55-c56c-71bf-00a5-870e2f4dd07b@suse.de> ("Andreas =?utf-8?Q?F=C3=A4rber=22's?= message of "Wed, 18 Jan 2017 23:38:48 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v0INf06O005679 Andreas Färber writes: > Am 18.01.2017 um 10:35 schrieb Neil Armstrong: >> On 01/17/2017 11:54 PM, Andreas Färber wrote: >>> Cc: ada@kingnoval.com >>> Signed-off-by: Andreas Färber >>> --- >>> Originally I thought we would group by SoC (6, 8, 8b, gxbb, gxl, gmx, etc.) >>> but this got out of order with nexbox,a95x - so inserting kingnovel between >>> amlogic and nexbox here. If that's what we want going forward, we should move >>> the old entries to make the scheme clearer. The alternative would be to >>> reorder alphabetically within each SoC group, but nexbox,a95x with two SoCs >>> makes it difficult to categorize, we could choose gxbb as the earlier one. >> >> Andreas, >> >> Feel free to provide a fixup. > > Sure, the question is which way. ;) Kevin? Carlo? I don't have a strong preference, but continuing to group by SoC makes the most sense based on what we have there now. Moving nexbox,a95x up to the first one (gxbb) is fine with me. Kevin