linux-kernel - Re: [PATCH v4] 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <15573018-32df-b67f-fc37-44da0ed7afde@landley.net>
Date:   Sat, 14 Jan 2023 17:45:59 -0600
From:   Rob Landley <rob@...dley.net>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Sergey Shtylyov <s.shtylyov@....ru>
Cc:     Rich Felker <dalias@...c.org>, linux-sh@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v4] sh: avoid using IRQ0 on SH3/4

On 1/13/23 12:38, John Paul Adrian Glaubitz wrote:
>>> The patch is against Linus Torvalds' 'linux.git' repo.
>> 
>>   So, this patch hasn't been merged... may I ask why? :-(
> 
> The SH maintainers have been MIA which is why the other maintainers want to kill the architecture again.

To clarify: Sato-san was only ever assisting Rich, as in promising to answer
questions when Rich didn't understand something. (That may not have been
represented in MAINTAINERS but that was what Sato-san agreed to when we all had
lunch together in tokyo however many years ago that was.)

> I’m seriously considering adopting the architecture.
> 
> Not sure whether Linus would grant that though.

I'll happily endorse you for maintainer if that would help.

Rob