Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: [PATCH v6] sh: avoid using IRQ0 on SH3/4
To:     John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
        Sergey Shtylyov <s.shtylyov@omp.ru>,
        Rich Felker <dalias@libc.org>, linux-sh@vger.kernel.org
Cc:     Yoshinori Sato <ysato@users.sourceforge.jp>,
        linux-kernel@vger.kernel.org
References: <71105dbf-cdb0-72e1-f9eb-eeda8e321696@omp.ru>
 <983d701befce7fc0010c53d09be84f5c330bdf45.camel@physik.fu-berlin.de>
From:   Sergei Shtylyov <sergei.shtylyov@gmail.com>
Message-ID: <837a586e-5e76-7a5b-a890-403ce26ea51b@gmail.com>
Date:   Sat, 10 Jun 2023 13:24:56 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <983d701befce7fc0010c53d09be84f5c330bdf45.camel@physik.fu-berlin.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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. :-)

> Adrian

MBR, Sergey