From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Rich Felker <dalias@libc.org>, <linux-sh@vger.kernel.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] sh: avoid using IRQ0 on SH3/4
Date: Mon, 12 Jun 2023 13:56:29 +0300 [thread overview]
Message-ID: <f32a649e-3563-2485-234e-640f9dace105@omp.ru> (raw)
In-Reply-To: <3fff103bcea3874cc7fd93c3a765ca642aa7f632.camel@physik.fu-berlin.de>
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
next prev parent reply other threads:[~2023-06-12 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 20:22 Sergey Shtylyov
2023-06-02 9:01 ` John Paul Adrian Glaubitz
2023-06-10 4:32 ` John Paul Adrian Glaubitz
2023-06-10 10:24 ` Sergei Shtylyov
2023-06-11 5:28 ` John Paul Adrian Glaubitz
2023-06-12 10:56 ` Sergey Shtylyov [this message]
2023-06-12 11:01 ` John Paul Adrian Glaubitz
2023-06-13 19:54 ` Sergey Shtylyov
2023-06-10 4:56 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f32a649e-3563-2485-234e-640f9dace105@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sergei.shtylyov@gmail.com \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®