linux-kernel - Re: [PATCH v7 0/2] Add support for Layerscape external interrupt lines

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: <8e1877ab5a1fecace3b2383789bdf404@www.loen.fr>
Date:   Tue, 12 Nov 2019 12:07:47 +0109
From:   Marc Zyngier <maz@...nel.org>
To:     Rasmus Villemoes <linux@...musvillemoes.dk>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Jason Cooper <jason@...edaemon.net>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        Kurt Kanzenbach <kurt@...utronix.de>,
        Vladimir Oltean <olteanv@...il.com>
Subject: Re: [PATCH v7 0/2] Add support for Layerscape external interrupt  lines

On 2019-11-12 11:27, Rasmus Villemoes wrote:
> On 11/11/2019 11.24, Marc Zyngier wrote:
>> On 2019-11-07 13:30, Rasmus Villemoes wrote:
>
>>> Rasmus Villemoes (2):
>>>   dt/bindings: Add bindings for Layerscape external irqs
>>>   irqchip: add support for Layerscape external interrupt lines
>>>
>>>  .../interrupt-controller/fsl,ls-extirq.txt    |  49 +++++
>>>  drivers/irqchip/Kconfig                       |   4 +
>>>  drivers/irqchip/Makefile                      |   1 +
>>>  drivers/irqchip/irq-ls-extirq.c               | 197 
>>> ++++++++++++++++++
>>>  4 files changed, 251 insertions(+)
>>>  create mode 100644
>>>
>>> 
>>> Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt
>>>  create mode 100644 drivers/irqchip/irq-ls-extirq.c
>>
>> Applied to irqchip-next.
>
> Thanks! Can I assume that branch doesn't get rebased so 87cd38dfd9e6 
> is
> a stable SHA1? I want to send a patch adding the node to 
> ls1021a.dtsi,
> and I hope not to have to wait another release cycle.

I usually try to avoid rebasing it, unless something really bad shows 
up.

Now, just adding a node to a DT shouldn't break anything, right? You
should be able to do that change and get things working magically once
this code hits mainline.

Or am I missing something?

         M.
-- 
Jazz is not dead. It just smells funny...