linux-kernel - Re: [PATCH v2 4/7] dt-bindings: tegra: Add missing chips and NVIDIA boards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180212144243.5ovljzk2heu3ccck@rob-hp-laptop>
Date:   Mon, 12 Feb 2018 08:42:43 -0600
From:   Rob Herring <robh@...nel.org>
To:     Mikko Perttunen <cyndis@...si.fi>
Cc:     Mikko Perttunen <mperttunen@...dia.com>, thierry.reding@...il.com,
        jonathanh@...dia.com, mark.rutland@....com, talho@...dia.com,
        linux-tegra@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 4/7] dt-bindings: tegra: Add missing chips and NVIDIA
 boards

On Sat, Feb 10, 2018 at 10:45:35AM +0200, Mikko Perttunen wrote:
> On 02/10/2018 12:49 AM, Rob Herring wrote:
> > On Tue, Feb 06, 2018 at 09:22:34AM +0200, Mikko Perttunen wrote:
> > > Add compatibility strings for supported but undocumented Tegra chips
> > > (Tegra114/124/132/210/186/194) and reference boards.
> > > 
> > > Signed-off-by: Mikko Perttunen <mperttunen@...dia.com>
> > > ---
> > > 
> > > Notes:
> > >      v2:
> > >      - add patch
> > > 
> > >   Documentation/devicetree/bindings/arm/tegra.txt | 16 ++++++++++++++++
> > >   1 file changed, 16 insertions(+)
> > > 
> > > diff --git a/Documentation/devicetree/bindings/arm/tegra.txt b/Documentation/devicetree/bindings/arm/tegra.txt
> > > index 7f1411bbabf7..32f62bb7006d 100644
> > > --- a/Documentation/devicetree/bindings/arm/tegra.txt
> > > +++ b/Documentation/devicetree/bindings/arm/tegra.txt
> > > @@ -9,6 +9,12 @@ following compatible values:
> > >     nvidia,tegra20
> > >     nvidia,tegra30
> > > +  nvidia,tegra114
> > > +  nvidia,tegra124
> > > +  nvidia,tegra132
> > > +  nvidia,tegra210
> > 
> > Some reason why this is not in numerical order?
> 
> They are in chronological/chip generation order, and for whatever reason,
> that isn't numerical.

Okay.

Reviewed-by: Rob Herring <robh@...nel.org>