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]

Message-ID: <3fff103bcea3874cc7fd93c3a765ca642aa7f632.camel@physik.fu-berlin.de>
Date:   Sun, 11 Jun 2023 07:28:45 +0200
From:   John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To:     Sergei Shtylyov <sergei.shtylyov@...il.com>,
        Sergey Shtylyov <s.shtylyov@....ru>,
        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 Sat, 2023-06-10 at 13:24 +0300, Sergei Shtylyov wrote:
> On 6/10/23 7:32 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.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913