linux-kernel - Re: [PATCH v6] sh: avoid using IRQ0 on SH3/4

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]

Date:   Mon, 12 Jun 2023 13:56:29 +0300
From:   Sergey Shtylyov <s.shtylyov@....ru>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Sergei Shtylyov <sergei.shtylyov@...il.com>,
        Rich Felker <dalias@...c.org>, <linux-sh@...r.kernel.org>
CC:     Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6] sh: avoid using IRQ0 on SH3/4

On 6/11/23 8:28 AM, John Paul Adrian Glaubitz wrote:
[...]

>>>> IRQ0 is no longer returned by platform_get_irq() and its ilk -- they now
>>>> return -EINVAL instead.  However, the kernel code supporting SH3/4 based
>>>> SoCs still maps the IRQ #s starting at 0 -- modify that code to start the
>>>> IRQ #s from 16 instead.
>>>>
>>>> The patch should mostly affect the AP-SH4A-3A/AP-SH4AD-0A boards as they
>>>> indeed are using IRQ0 for the SMSC911x compatible Ethernet chip...
>>>
>>> Do you mind if I remove the ellipsis at the end of this sentence when I merge
>>> this later today? I think it makes no sense from a grammatical point of view.
>>
>>    No, I don't mind. :-)
> 
> Applied to my for-next branch.

   Note that this was positioned as a fix.
   Where is your tree, BTW? :-)

> Thanks,
> Adrian

MBR, Sergey