linux-kernel - Re: [PATCH v8 5/5] MIPS: DTS: img: Fix schema warnings for pwm-leds

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]

Message-ID: <20201207103221.GA15686@alpha.franken.de>
Date:   Mon, 7 Dec 2020 11:32:21 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Alexander Dahl <post@...pocky.de>
Cc:     Rob Herring <robh+dt@...nel.org>, Alexander Dahl <ada@...rsis.com>,
        linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-amlogic@...ts.infradead.org, linux-mips@...r.kernel.org,
        James Hartley <james.hartley@...drel.com>,
        Rahul Bedarkar <rahulbedarkar89@...il.com>
Subject: Re: [PATCH v8 5/5] MIPS: DTS: img: Fix schema warnings for pwm-leds

On Sat, Nov 28, 2020 at 10:53:53PM +0100, Alexander Dahl wrote:
> The node names for devices using the pwm-leds driver follow a certain
> naming scheme (now).  Parent node name is not enforced, but recommended
> by DT project.
> 
> Signed-off-by: Alexander Dahl <post@...pocky.de>
> ---
> 
> Notes:
>     v7 -> v8:
>       * rebased on v5.10-rc1
>     
>     v6 -> v7:
>       * added another explaining sentence to commit message
>     
>     v6:
>       * added this patch to series
> 
>  arch/mips/boot/dts/img/pistachio_marduk.dts | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]