From: Andrew Lunn <andrew@lunn.ch>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: netdev@vger.kernel.org, linus.walleij@linaro.org,
alsi@bang-olufsen.dk, 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, arinc.unal@arinc9.com
Subject: Re: [PATCH net v2 2/2] net: dsa: realtek: remove realtek,rtl8367s string
Date: Tue, 19 Apr 2022 01:48:23 +0200 [thread overview]
Message-ID: <Yl34x+GDBkBKBggN@lunn.ch> (raw)
In-Reply-To: <20220418233558.13541-2-luizluca@gmail.com>
On Mon, Apr 18, 2022 at 08:35:58PM -0300, Luiz Angelo Daros de Luca wrote:
> There is no need to add new compatible strings for each new supported
> chip version. The compatible string is used only to select the subdriver
> (rtl8365mb.c or rtl8366rb.c). Once in the subdriver, it will detect the
> chip model by itself, ignoring which compatible string was used.
>
> Link: https://lore.kernel.org/netdev/20220414014055.m4wbmr7tdz6hsa3m@bang-olufsen.dk/
> Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
> Reviewed-by: Alvin Šipraga <alsi@bang-olufsen.dk>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2022-04-18 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 23:35 [PATCH net v2 1/2] dt-bindings: net: dsa: realtek: cleanup compatible strings Luiz Angelo Daros de Luca
2022-04-18 23:35 ` [PATCH net v2 2/2] net: dsa: realtek: remove realtek,rtl8367s string Luiz Angelo Daros de Luca
2022-04-18 23:48 ` Andrew Lunn [this message]
2022-04-19 0:43 ` Arınç ÜNAL
2022-04-18 23:48 ` [PATCH net v2 1/2] dt-bindings: net: dsa: realtek: cleanup compatible strings Andrew Lunn
2022-04-19 0:47 ` Arınç ÜNAL
2022-04-19 13:10 ` Alvin Šipraga
2022-04-19 13:13 ` Alvin Šipraga
2022-04-20 10:10 ` patchwork-bot+netdevbpf
2022-04-20 20:29 ` Luiz Angelo Daros de Luca
2022-04-22 17:56 ` Jakub Kicinski
2022-04-25 18:48 ` Rob Herring
2022-04-27 21:43 ` Luiz Angelo Daros de Luca
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=Yl34x+GDBkBKBggN@lunn.ch \
--to=andrew@lunn.ch \
--cc=alsi@bang-olufsen.dk \
--cc=arinc.unal@arinc9.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.