[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46bf2a4e-fdf4-fba1-f0de-0df2496b0c36@omp.ru>
Date: Sun, 28 Jan 2024 21:23:27 +0300
From: Sergey Shtylyov <s.shtylyov@....ru>
To: Claudiu <claudiu.beznea@...on.dev>, <davem@...emloft.net>,
<edumazet@...gle.com>, <kuba@...nel.org>, <pabeni@...hat.com>,
<richardcochran@...il.com>, <p.zabel@...gutronix.de>,
<geert+renesas@...der.be>
CC: <netdev@...r.kernel.org>, <linux-renesas-soc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Claudiu Beznea
<claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH net-next v4 08/15] net: ravb: Move the IRQs get and
request in the probe function
On 1/28/24 9:03 PM, Sergey Shtylyov wrote:
[...]
>> I suggest the following subject "net: ravb: Move getting/requesting IRQs in
>> the probe() method".
Or the probe() API, if you prefer this naming...
> Oops, s/in/to/. :-)
Well, we don't move getting IRQs to the probe() method, but
we move the platform_get_irq[_byname]() calls to a separate function.
So, perhaps "in" was good... :-)
[...]
MBR, Sergey
Powered by blists - more mailing lists