[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b16bd774-b641-f1b6-49f5-9ea5e3498ee7@bang-olufsen.dk>
Date: Sat, 28 Aug 2021 10:50:18 +0000
From: Alvin Šipraga <ALSI@...g-olufsen.dk>
To: Linus Walleij <linus.walleij@...aro.org>,
Andrew Lunn <andrew@...n.ch>
CC: Alvin Šipraga <alvin@...s.dk>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Michael Rasmussen <MIR@...g-olufsen.dk>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH net-next 1/5] net: dsa: realtek-smi: fix mdio_free bug
on module unload
On 8/28/21 12:06 AM, Linus Walleij wrote:
> On Mon, Aug 23, 2021 at 1:16 AM Andrew Lunn <andrew@...n.ch> wrote:
>
>>> No, there isn't. I neglected to mention in the rtl8365mb patch that I
>>> reworked the IRQ setup (compared with rtl8366rb) so that it could be
>>> torn down in a neat way. So you will see that the new driver does it
>>> properly, but I did not touch rtl8366rb because I am not using it. I am
>>> happy to do the same to rtl8366rb but I don't think I should make it
>>> part of this series. What do you think?
>>
>> Lets see if Linus has time. He can probably model the change based on
>> what you have done here.
>
> I have limited bandwidth as I am effectively on parental leave, so
> I can't do much of writing code, but I can certainly test a patch or
> two.
No problem - I will follow up on this and submit some patches when I get
there.
Alvin
>
> Yours,
> Linus Walleij
>
Powered by blists - more mailing lists