linux-kernel - Re: [PATCH] ARM: dts: tpc: Device tree description of the TPC board

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] [day] [month] [year] [list]

Date:   Sat, 3 Mar 2018 09:38:28 -0300
From:   Fabio Estevam <festevam@...il.com>
To:     Lukasz Majewski <lukma@...x.de>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        Mark Rutland <mark.rutland@....com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>, Russell King <linux@...linux.org.uk>,
        Rob Herring <robh+dt@...nel.org>,
        Sascha Hauer <kernel@...gutronix.de>,
        Fabio Estevam <fabio.estevam@....com>,
        Shawn Guo <shawnguo@...nel.org>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: dts: tpc: Device tree description of the TPC board

Hi Lukasz,

On Sat, Mar 3, 2018 at 4:06 AM, Lukasz Majewski <lukma@...x.de> wrote:

> Previously (for other imx6q board) I've added entry to e.g.
> panel-simple.c file [1] to describe the display.
>
> I thought that adding timings to DTS is more welcome - hence we do not
> need to add any extra code to Linux when porting new board?

Adding an entry to panel-simple helps when people want to use this
panel into their dts, as they need only to pass a compatible string
line instead of passing all the LCD timings.

> The other upstreamed imx6q board used dual license - GPLv2 or X11
> (which is also called MIT license).
>
> I suppose that this license header shall be replaced with:
>
> SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>
> Am I correct?

Yes, correct.