From: Andrew Lunn <andrew@lunn.ch>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: "Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"tobias@waldekranz.com" <tobias@waldekranz.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"vladimir.oltean@nxp.com" <vladimir.oltean@nxp.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>
Subject: Re: [PATCH net-next] net: dsa: realtek: add compatible strings for RTL8367RB-VB
Date: Thu, 14 Apr 2022 15:48:11 +0200 [thread overview]
Message-ID: <YlgmG3mLlRKef+sy@lunn.ch> (raw)
In-Reply-To: <20220414113718.ofhgzhsmvyuxd2l2@bang-olufsen.dk>
> > Is it too late to get rid of all those compatible strings from
> > dt-bindings? And rtl8367s from the driver?
> > We must add all supported devices to the doc as well, similar to mv88e6085.
>
> You can always try! I'm OK with those things in principle, but others might
> object due to ABI reasons.
Anything which is in a released Linus kernel is ABI and cannot be
removed. Anything in net-next, or an -rcX kernel can still be changed.
Andrew
next prev parent reply other threads:[~2022-04-14 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:04 [PATCH net-next] net: dsa: realtek: add compatible strings for RTL8367RB-VB Luiz Angelo Daros de Luca
2022-04-12 0:18 ` Andrew Lunn
2022-04-12 4:12 ` Luiz Angelo Daros de Luca
2022-04-12 12:43 ` Andrew Lunn
2022-04-12 13:30 ` Alvin Šipraga
2022-04-13 18:29 ` Luiz Angelo Daros de Luca
2022-04-13 18:40 ` Andrew Lunn
2022-04-14 1:40 ` Alvin Šipraga
2022-04-12 10:50 ` Alvin Šipraga
2022-04-13 18:38 ` Luiz Angelo Daros de Luca
2022-04-14 1:45 ` Alvin Šipraga
2022-04-14 2:32 ` Luiz Angelo Daros de Luca
2022-04-14 11:37 ` Alvin Šipraga
2022-04-14 13:48 ` Andrew Lunn [this message]
2022-04-15 7:48 ` Luiz Angelo Daros de Luca
2022-04-15 14:35 ` Andrew Lunn
2022-04-16 6:27 ` 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=YlgmG3mLlRKef+sy@lunn.ch \
--to=andrew@lunn.ch \
--cc=ALSI@bang-olufsen.dk \
--cc=arinc.unal@arinc9.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).