linux-kernel - Re: [PATCH v2 07/30] arm: dts: mt7623: add pinctrl nodes to the mt7623 dtsi file

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: <CACRpkda8bu3zT_kLWSbfx1SobHcQRxEOdJC=PEpW4=+LvcmiMA@mail.gmail.com>
Date:   Fri, 28 Apr 2017 10:03:43 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     sean.wang@...iatek.com
Cc:     Rob Herring <robh+dt@...nel.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        John Crispin <john@...ozen.org>,
        Mark Rutland <mark.rutland@....com>,
        Russell King <linux@...linux.org.uk>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "moderated list:ARM/Mediatek SoC support" 
        <linux-mediatek@...ts.infradead.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 07/30] arm: dts: mt7623: add pinctrl nodes to the
 mt7623 dtsi file

On Wed, Apr 26, 2017 at 11:25 AM,  <sean.wang@...iatek.com> wrote:

> From: John Crispin <john@...ozen.org>
>
> Add pin controller node to the mt7623.dtsi file
>
> Signed-off-by: John Crispin <john@...ozen.org>
> Signed-off-by: Sean Wang <sean.wang@...iatek.com>
(...)
> +       pio: pinctrl@...05000 {
> +               compatible = "mediatek,mt7623-pinctrl",
> +                            "mediatek,mt2701-pinctrl";

This looks right. And that is why we should not delete that compatible
string.

Reviewed-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij