All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Pal <kuncy7@gmail.com>
To: Johan Alvarado <contact@c127.dev>,
	Linus Walleij <linusw@kernel.org>,
	Alvin Sipraga <alsi@bang-olufsen.dk>,
	Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Russell King <linux@armlinux.org.uk>
Cc: Mieczyslaw Nalewaj <namiltd@yahoo.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Luiz Angelo Daros de Luca <luizluca@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/2] net: dsa: realtek: rtl8365mb: add SGMII/HSGMII support for RTL8367S
Date: Wed, 22 Jul 2026 10:23:21 +0200	[thread overview]
Message-ID: <20260722082321.13802-1-kuncy7@gmail.com> (raw)
In-Reply-To: <20260711-rtl8367s-sgmii-v6-0-88f7944ddca7@c127.dev>

Hi Johan, Luiz,

Here is the tag, as offered.

The board is a TP-Link Archer AX55 v1 (IPQ5018 + RTL8367S). Its
CPU-facing port runs fixed 2500base-x, so what this exercises is the
HSGMII path of 2/2 on top of the SerDes plumbing added by 1/2; the
1000base-x path is not reachable on this hardware. The trunk has been
carrying traffic continuously for days, with zero FCS errors and zero
drop events on either side of it.

The final cold soak on the healthy power supply came out clean this
morning as well, so the cold-start failure I reported earlier in this
thread is settled as a failing PSU rather than anything in the driver.

Tested-by: Stanislaw Pal <kuncy7@gmail.com>

Best regards,
Stanislaw

      parent reply	other threads:[~2026-07-22  8:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12  4:31 [PATCH net-next v6 0/2] net: dsa: realtek: rtl8365mb: add SGMII/HSGMII support for RTL8367S Johan Alvarado via B4 Relay
2026-07-12  4:31 ` Johan Alvarado
2026-07-12  4:31 ` [PATCH net-next v6 1/2] net: dsa: realtek: rtl8365mb: add SGMII " Johan Alvarado via B4 Relay
2026-07-12  4:31   ` Johan Alvarado
2026-07-12  8:23   ` Maxime Chevallier
2026-07-16  6:40   ` Mieczyslaw Nalewaj
2026-07-17 12:51     ` Stanislaw
2026-07-17 16:28       ` Mieczyslaw Nalewaj
2026-07-17 22:12     ` Johan Alvarado
2026-07-18  5:40       ` Luiz Angelo Daros de Luca
2026-07-18  7:55         ` Stanislaw
2026-07-19  1:09           ` Luiz Angelo Daros de Luca
2026-07-19  7:35             ` Stanislaw
2026-07-21 11:53             ` Stanislaw
2026-07-21 14:32   ` Mieczyslaw Nalewaj
2026-07-12  4:31 ` [PATCH net-next v6 2/2] net: dsa: realtek: rtl8365mb: add HSGMII " Johan Alvarado via B4 Relay
2026-07-12  4:31   ` Johan Alvarado
2026-07-12 18:05   ` Mieczyslaw Nalewaj
2026-07-14  0:24     ` Johan Alvarado
2026-07-18  5:46       ` Luiz Angelo Daros de Luca
2026-07-13  8:14   ` Stacho_P
2026-07-21 14:32   ` Mieczyslaw Nalewaj
2026-07-22  8:23 ` Stanislaw Pal [this message]

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=20260722082321.13802-1-kuncy7@gmail.com \
    --to=kuncy7@gmail.com \
    --cc=alsi@bang-olufsen.dk \
    --cc=andrew@lunn.ch \
    --cc=contact@c127.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luizluca@gmail.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=namiltd@yahoo.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.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.