From: Vladimir Oltean <olteanv@gmail.com>
To: Sergei Antonov <saproj@gmail.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: mv88e6060: add phylink_get_caps implementation
Date: Thu, 10 Aug 2023 21:31:18 +0300 [thread overview]
Message-ID: <20230810183118.3z77lrnun5pukgfa@skbuf> (raw)
In-Reply-To: <CABikg9zcNED55rjnq9a9ZTjp8pCKXWs9HBy5r2KAdECP1Dm8vg@mail.gmail.com>
On Thu, Aug 10, 2023 at 09:17:33PM +0300, Sergei Antonov wrote:
> I am planning to submit a platform using "marvell,mv88e6060". For the
> next release cycle hopefully.
> Our should I rather try to move MV88E6060 support to /mv88e6xxx?
Device tree bindings and the driver implementation should be seen as
separate things. You can submit a platform for mv88e6060 regardless of
what driver it's using, and if the driver is merged into mv88e6xxx, that
needs to support the existing platforms as well.
next prev parent reply other threads:[~2023-08-10 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:46 [PATCH net-next v2] net: dsa: mv88e6060: add phylink_get_caps implementation Russell King (Oracle)
2023-08-10 16:44 ` Vladimir Oltean
2023-08-10 16:52 ` Russell King (Oracle)
2023-08-10 17:11 ` Vladimir Oltean
2023-08-10 17:38 ` Russell King (Oracle)
2023-08-10 18:17 ` Sergei Antonov
2023-08-10 18:31 ` Vladimir Oltean [this message]
2023-08-10 18:27 ` Vladimir Oltean
2023-08-10 18:09 ` Sergei Antonov
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=20230810183118.3z77lrnun5pukgfa@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saproj@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;
as well as URLs for NNTP newsgroup(s).