From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>, netdev@vger.kernel.org
Cc: linus.walleij@linaro.org, alsi@bang-olufsen.dk, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org, krzk+dt@kernel.org
Subject: Re: [PATCH net-next RFC 0/3] net: dsa: realtek: drop custom slave MII
Date: Wed, 29 Jun 2022 15:30:03 +0300 [thread overview]
Message-ID: <6f4e00d6-6b7d-e4c7-8108-67c009f7a6d8@arinc9.com> (raw)
In-Reply-To: <20220629035434.1891-1-luizluca@gmail.com>
On 29.06.2022 06:54, Luiz Angelo Daros de Luca wrote:
> The last patch cleans all the deprecated code while keeping the kernel
> messages. However, if there is no "mdio" node but there is a node with
> the old compatible stings "realtek,smi-mdio", it will show an error. It
> should still work but it will use polling instead of interruptions.
>
> My idea, if accepted, is to submit patches 1 and 2 now. After a
> reasonable period, submit patch 3.
>
> I don't have an SMI-connected device and I'm asking for testers. It
> would be nice to test the first 2 patches with:
I'd love to test this on an Asus RT-AC88U which has got the
smi-connected RTL8365MB switch but modifying the OpenWrt SDK to build
for latest kernels is a really painful process. I know it's not related
to this patch series but, does anyone know a more efficient way of
building the kernel with rootfs with sufficent userspace tools? Like, am
I supposed to use Buildroot, Yocto?
Arınç
next prev parent reply other threads:[~2022-06-29 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 3:54 [PATCH net-next RFC 0/3] net: dsa: realtek: drop custom slave MII Luiz Angelo Daros de Luca
2022-06-29 3:54 ` [PATCH net-next RFC 1/3] net: dsa: realtek: rename switch_ops to its usage, not users Luiz Angelo Daros de Luca
2022-06-29 3:54 ` [PATCH net-next RFC 2/3] net: dsa: realtek: deprecate custom slave mii Luiz Angelo Daros de Luca
2022-06-29 3:54 ` [PATCH net-next RFC 3/3] net: dsa: realtek: remove deprecated " Luiz Angelo Daros de Luca
2022-06-29 12:30 ` Arınç ÜNAL [this message]
2022-06-29 16:49 ` [PATCH net-next RFC 0/3] net: dsa: realtek: drop custom slave MII Luiz Angelo Daros de Luca
2022-06-29 16:43 ` Luiz Angelo Daros de Luca
2022-06-29 18:14 ` Alvin Šipraga
2022-06-29 18:31 ` Alvin Šipraga
2022-06-30 17:05 ` Luiz Angelo Daros de Luca
2022-06-30 20:04 ` Alvin Šipraga
2022-07-06 15:29 ` Vladimir Oltean
2022-07-07 8:45 ` Linus Walleij
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=6f4e00d6-6b7d-e4c7-8108-67c009f7a6d8@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.com \
/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