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: <160769813659.482133.8392979950247989648.b4-ty@kernel.org>
Date:   Fri, 11 Dec 2020 15:01:32 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     shawnguo@...nel.org, linux@...musvillemoes.dk, leoyang.li@....com,
        mark.rutland@....com, zhiqiang.hou@....com,
        Biwen Li <biwen.li@....nxp.com>, robh+dt@...nel.org,
        tglx@...utronix.de
Cc:     xiaobo.xie@....com, Hou Zhiqiang <Zhiqiang.Hou@....com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Biwen Li <biwen.li@....com>, linux-kernel@...r.kernel.org,
        jiafei.pan@....com
Subject: Re: [v4 01/11] irqchip: ls-extirq: Add LS1043A, LS1088A external interrupt

On Mon, 30 Nov 2020 18:15:05 +0800, Biwen Li wrote:
> Add an new IRQ chip declaration for LS1043A and LS1088A
> - compatible "fsl,ls1043a-extirq" for LS1043A, LS1046A.
> - compatible "fsl,ls1088a-extirq" for LS1088A, LS208xA, LX216xA.
> - get mask value directly according to compatible property of DT
>   and remove confused code(bit_reverse field of struct ls_extirq_data,
>   no need this field for SoC LS1021A. Because the register
>   LS1021A_SCFGREVCR is initialized to 0xffffffff by the relative rcw)

Applied to irq/irqchip-next, thanks!

[01/11] irqchip: ls-extirq: Add LS1043A, LS1088A external interrupt
        commit: b16a1caf4686895427c810219d4b2f796e676160
[11/11] dt-bindings: interrupt-controller: update bindings for supporting more SoCs
        commit: 9898a59358d7cb925f63bb77bd40224d1bc4857e

Patches 2-10 should be routed via the SoC tree.

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ