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]
Date:   Wed, 25 Oct 2023 09:16:47 +0200
From:   Krzysztof Kozlowski <>
To:     Huacai Chen <>, Marc Zyngier <>
Cc:     Binbin Zhou <>,
        Jonas Gorski <>,
        Jiaxun Yang <>,
        Binbin Zhou <>,
        Huacai Chen <>,
        Thomas Gleixner <>,
        Rob Herring <>,
        Krzysztof Kozlowski <>,
        Conor Dooley <>,,,
        Thomas Bogendoerfer <>,,,,
Subject: Re: [PATCH v2] dt-bindings: interrupt-controller: loongson,liointc:
 Fix warnings about liointc-2.0

On 25/10/2023 03:56, Huacai Chen wrote:
> Hi, Krzysztof,
> On Fri, Oct 20, 2023 at 8:18 PM Marc Zyngier <> wrote:
>> On Fri, 20 Oct 2023 10:51:35 +0100,
>> Binbin Zhou <> wrote:
>>> Hi Krzysztof & Marc:
>>> Sorry for the interruption.
>>> As said before, we tried to use the 'interrupt-map attribute' in our
>>> Loongson liointc dts(i), but there are some unfriendly points.
>>> Do you have any other different suggestions?
>> I don't have any suggestion, but if you are still thinking of adding
>> some extra crap to the of_irq_imap_abusers[] array, the answer is a
>> firm 'NO'.
> Excuse me, but as described before, 'interrupt-map' cannot be used for
> liointc unless adding it to of_irq_imap_abusers[], can we still use
> 'parent_int_map' in this case? Or just change it to 'parent-int-map'
> to satisfy the naming style?

Why do you respond to me? You received firm 'NO' about
of_irq_imap_abusers, so how adhering to naming style or violating naming
style has anything to do with it?

Best regards,

Powered by blists - more mailing lists