From: Vladimir Oltean <olteanv@gmail.com>
To: Tristram.Ha@microchip.com
Cc: Woojung Huh <woojung.huh@microchip.com>,
Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: microchip: Add SGMII port support to KSZ9477 switch
Date: Tue, 14 Jan 2025 18:53:12 +0200 [thread overview]
Message-ID: <20250114165312.zfsozrtud5wqjn5s@skbuf> (raw)
In-Reply-To: <20250114160908.les2vsq42ivtrvqe@skbuf>
On Tue, Jan 14, 2025 at 06:09:08PM +0200, Vladimir Oltean wrote:
> There is way too much that seems unjustifiably complex at this stage,
> including this. I would like to see a v3 using xpcs + the remaining
> required delta for ksz9477, ideally with no internal PHY simulation.
> Then we can go from there.
You might stumble upon this issue on net-next, which you've helped me
remember I should upstream, so I posted 2 patches just now:
https://lore.kernel.org/netdev/20250114164721.2879380-1-vladimir.oltean@nxp.com/
next prev parent reply other threads:[~2025-01-14 16:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 2:47 [PATCH net-next v2] net: dsa: microchip: Add SGMII port support to KSZ9477 switch Tristram.Ha
2025-01-14 16:09 ` Vladimir Oltean
2025-01-14 16:53 ` Vladimir Oltean [this message]
2025-01-15 10:10 ` Maxime Chevallier
2025-01-17 0:56 ` Tristram.Ha
2025-01-17 13:36 ` Andrew Lunn
2025-01-18 0:59 ` Tristram.Ha
2025-01-18 1:26 ` Vladimir Oltean
2025-01-18 4:07 ` Tristram.Ha
2025-01-18 20:00 ` Andrew Lunn
2025-01-21 0:28 ` Tristram.Ha
2025-01-21 3:08 ` Tristram.Ha
2025-01-17 16:18 ` Vladimir Oltean
2025-01-17 0:51 ` Tristram.Ha
-- strict thread matches above, loose matches on Subject: below --
2025-05-07 0:09 Tristram.Ha
2025-05-07 7:44 ` Maxime Chevallier
2025-05-07 8:31 ` Russell King (Oracle)
2025-05-07 8:54 ` Maxime Chevallier
2025-05-08 1:41 ` Tristram.Ha
2025-05-10 0:41 ` Jakub Kicinski
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=20250114165312.zfsozrtud5wqjn5s@skbuf \
--to=olteanv@gmail.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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