linux-kernel - Re: [PATCH 0/7] mips: bmips: include dt-bindings headers

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: <20210312102924.GF7027@alpha.franken.de>
Date:   Fri, 12 Mar 2021 11:29:24 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Álvaro Fernández Rojas <noltari@...il.com>
Cc:     jonas.gorski@...il.com, Florian Fainelli <f.fainelli@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        bcm-kernel-feedback-list@...adcom.com, linux-mips@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] mips: bmips: include dt-bindings headers

On Wed, Feb 24, 2021 at 10:38:49AM +0100, Álvaro Fernández Rojas wrote:
> Allow including dt-bindings header files for bcm63xx.
> 
>  v2: remove irqs header and add more bindings.
> 
> Álvaro Fernández Rojas (7):
>   mips: dts: brcm: allow including header files
>   mips: bmips: bcm3368: include dt-bindings
>   mips: bmips: bcm6328: include dt-bindings
>   mips: bmips: bcm6358: include dt-bindings
>   mips: bmips: bcm6362: include dt-bindings
>   mips: bmips: bcm6368: include dt-bindings
>   mips: bmips: bcm63268: include dt-bindings
> 
>  arch/mips/boot/dts/brcm/bcm3368-netgear-cvg834g.dts    | 2 +-
>  arch/mips/boot/dts/brcm/bcm3368.dtsi                   | 3 +++
>  arch/mips/boot/dts/brcm/bcm63268-comtrend-vr-3032u.dts | 2 +-
>  arch/mips/boot/dts/brcm/bcm63268.dtsi                  | 5 +++++
>  arch/mips/boot/dts/brcm/bcm6328.dtsi                   | 5 +++++
>  arch/mips/boot/dts/brcm/bcm6358-neufbox4-sercomm.dts   | 2 +-
>  arch/mips/boot/dts/brcm/bcm6358.dtsi                   | 4 ++++
>  arch/mips/boot/dts/brcm/bcm6362-neufbox6-sercomm.dts   | 2 +-
>  arch/mips/boot/dts/brcm/bcm6362.dtsi                   | 5 +++++
>  arch/mips/boot/dts/brcm/bcm6368.dtsi                   | 4 ++++
>  arch/mips/boot/dts/brcm/bcm93384wvg.dts                | 2 +-
>  arch/mips/boot/dts/brcm/bcm93384wvg_viper.dts          | 2 +-
>  arch/mips/boot/dts/brcm/bcm96368mvwg.dts               | 2 +-
>  arch/mips/boot/dts/brcm/bcm97125cbmb.dts               | 2 +-
>  arch/mips/boot/dts/brcm/bcm97346dbsmb.dts              | 4 ++--
>  arch/mips/boot/dts/brcm/bcm97358svmb.dts               | 4 ++--
>  arch/mips/boot/dts/brcm/bcm97360svmb.dts               | 2 +-
>  arch/mips/boot/dts/brcm/bcm97362svmb.dts               | 4 ++--
>  arch/mips/boot/dts/brcm/bcm97420c.dts                  | 2 +-
>  arch/mips/boot/dts/brcm/bcm97425svmb.dts               | 4 ++--
>  arch/mips/boot/dts/brcm/bcm97435svmb.dts               | 4 ++--
>  arch/mips/boot/dts/brcm/bcm9ejtagprb.dts               | 2 +-
>  22 files changed, 47 insertions(+), 21 deletions(-)

series 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 ]