From: Kevin Hilman <khilman@baylibre.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org,
Carlo Caione <carlo@caione.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Wed, 18 Jan 2017 15:38:57 -0800 [thread overview]
Message-ID: <m2bmv4x7ji.fsf@baylibre.com> (raw)
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")
Andreas Färber <afaerber@suse.de> 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 <afaerber@suse.de>
>>> ---
>>> 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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Wed, 18 Jan 2017 15:38:57 -0800 [thread overview]
Message-ID: <m2bmv4x7ji.fsf@baylibre.com> (raw)
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")
Andreas Färber <afaerber@suse.de> 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 <afaerber@suse.de>
>>> ---
>>> 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Wed, 18 Jan 2017 15:38:57 -0800 [thread overview]
Message-ID: <m2bmv4x7ji.fsf@baylibre.com> (raw)
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")
Andreas F?rber <afaerber@suse.de> writes:
> Am 18.01.2017 um 10:35 schrieb Neil Armstrong:
>> On 01/17/2017 11:54 PM, Andreas F?rber wrote:
>>> Cc: ada at kingnoval.com
>>> Signed-off-by: Andreas F?rber <afaerber@suse.de>
>>> ---
>>> 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
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Wed, 18 Jan 2017 15:38:57 -0800 [thread overview]
Message-ID: <m2bmv4x7ji.fsf@baylibre.com> (raw)
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")
Andreas F?rber <afaerber@suse.de> writes:
> Am 18.01.2017 um 10:35 schrieb Neil Armstrong:
>> On 01/17/2017 11:54 PM, Andreas F?rber wrote:
>>> Cc: ada at kingnoval.com
>>> Signed-off-by: Andreas F?rber <afaerber@suse.de>
>>> ---
>>> 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
next prev parent reply other threads:[~2017-01-18 23:40 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 3:06 [PATCH 0/2] ARM64: meson-gxm: R-Box Pro enablement Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-17 22:54 ` [PATCH 1/3] Documentation: devicetree: Add Kingnovel vendor prefix Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 23:38 ` Kevin Hilman [this message]
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-17 22:54 ` [PATCH 3/3] ARM64: dts: meson-gxm-rbox-pro: Add board compatible string Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-21 20:01 ` [PATCH 1/3] Documentation: devicetree: Add Kingnovel vendor prefix Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-17 23:06 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-18 22:27 ` Kevin Hilman
2017-01-18 22:27 ` Kevin Hilman
2017-01-18 22:27 ` Kevin Hilman
2017-01-19 8:10 ` Neil Armstrong
2017-01-19 8:10 ` Neil Armstrong
2017-01-19 8:10 ` Neil Armstrong
2017-01-17 3:06 ` [PATCH 2/2] ARM64: dts: meson-gxm-rbox-pro: Enable Bluetooth Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2bmv4x7ji.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=afaerber@suse.de \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.