linux-kernel - Re: [PATCH 00/14] 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20200824231519.GA3507085@bogus>
Date:   Mon, 24 Aug 2020 17:15:19 -0600
From:   Rob Herring <robh@...nel.org>
To:     Álvaro Fernández Rojas <noltari@...il.com>
Cc:     f.fainelli@...il.com, tsbogend@...ha.franken.de,
        jonas.gorski@...il.com, bcm-kernel-feedback-list@...adcom.com,
        linux-mips@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/14] mips: bmips: include dt-bindings headers

On Wed, Aug 12, 2020 at 08:31:15AM +0200, Álvaro Fernández Rojas wrote:
> Allow including dt-bindings header files and use them for bcm63xx.
> 
> Álvaro Fernández Rojas (14):
>   mips: dts: brcm: allow including header files
>   mips: bmips: add BCM3368 irq definitions
>   mips: bmips: add BCM6318 irq definitions
>   mips: bmips: add BCM6328 irq definitions
>   mips: bmips: add BCM6358 irq definitions
>   mips: bmips: add BCM6362 irq definitions
>   mips: bmips: add BCM6368 irq definitions
>   mips: bmips: add BCM63268 irq definitions
>   mips: bmips: bcm3368: include and use dt-bindings
>   mips: bmips: bcm6328: include and use dt-bindings
>   mips: bmips: bcm6358: include and use dt-bindings
>   mips: bmips: bcm6362: include and use dt-bindings
>   mips: bmips: bcm6368: include and use dt-bindings
>   mips: bmips: bcm63268: include and use dt-bindings
> 
>  .../boot/dts/brcm/bcm3368-netgear-cvg834g.dts |  2 +-
>  arch/mips/boot/dts/brcm/bcm3368.dtsi          |  8 +-
>  .../dts/brcm/bcm63268-comtrend-vr-3032u.dts   |  2 +-
>  arch/mips/boot/dts/brcm/bcm63268.dtsi         | 12 ++-
>  arch/mips/boot/dts/brcm/bcm6328.dtsi          | 12 ++-
>  .../dts/brcm/bcm6358-neufbox4-sercomm.dts     |  2 +-
>  arch/mips/boot/dts/brcm/bcm6358.dtsi          | 12 ++-
>  .../dts/brcm/bcm6362-neufbox6-sercomm.dts     |  2 +-
>  arch/mips/boot/dts/brcm/bcm6362.dtsi          | 12 ++-
>  arch/mips/boot/dts/brcm/bcm6368.dtsi          | 12 ++-
>  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 +-
>  .../bcm3368-interrupt-controller.h            | 19 ++++
>  .../bcm6318-interrupt-controller.h            | 84 ++++++++++++++++++
>  .../bcm63268-interrupt-controller.h           | 86 +++++++++++++++++++
>  .../bcm6328-interrupt-controller.h            | 68 +++++++++++++++
>  .../bcm6358-interrupt-controller.h            | 38 ++++++++
>  .../bcm6362-interrupt-controller.h            | 71 +++++++++++++++
>  .../bcm6368-interrupt-controller.h            | 71 +++++++++++++++

You'll notice that there are essentially no other headers with 
SoC interrupt numbers. That's because we don't do defines for them. It's 
pointless obfuscation.

Rob