From: Mieczyslaw Nalewaj <namiltd@yahoo.com>
To: "Alvin Šipraga" <alvin.sipraga@analog.com>
Cc: linusw@kernel.org, andrew@lunn.ch, olteanv@gmail.com,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux@armlinux.org.uk, luizluca@gmail.com,
maxime.chevallier@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 04/10] net: dsa: realtek: rtl8365mb: set RGMII mode for family D
Date: Fri, 6 Nov 2026 17:43:06 +0100 [thread overview]
Message-ID: <29bfb266-8bd4-4c59-868a-cc27259c1f16@yahoo.com> (raw)
In-Reply-To: <au3t3XC2b0ZGLN4A@analog.com>
On <DATA>, Alvin Šipraga wrote:
> On Fri, Nov 06, 2026 at 03:56:18PM +0100, Mieczyslaw Nalewaj wrote:
> > I do not have the hardware, so I cannot read the reset default of
> > MAC4_SEL_EXT1 myself. [...]
>
> If you don't have the HW, how are you testing these patches...?
The code was tested by users of RTL8367S-VB devices from the OpenWrt
GitHub and the OpenWrt forum, who built it and reported back to me.
These were basic functionality tests only. I do not test it myself, and
I should have said so in the cover letter.
> I think we will need a Tested-by: tag from someone(s) with both a family
> C and D to get this series in, if you are unable to test things
> yourself.
Understood. I have already asked those users to respond on this mailing
list and give their Tested-by tags,
> Please also do not submit anything if it has not been tested. Maybe it
> was, but then please get that person's Tested-by and put them on
> CC. Otherwise maintainers might merge this assuming it was tested, if
> you got the reviews... It is a basic assumption that non-RFC stuff has
> been tested when posted to the list.
Noted, and sorry for the confusion.
Kind regards,
Mieczyslaw
next prev parent reply other threads:[~2026-11-06 16:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3bf4dd70-9771-497b-8c27-e925e0ef81eb.ref@yahoo.com>
2026-11-02 14:34 ` [PATCH net-next v7 0/10] net: dsa: realtek: rtl8365mb: add support for RTL8367S-VB Mieczyslaw Nalewaj
2026-11-02 14:36 ` [PATCH net-next v7 01/10] dt-bindings: net: dsa: realtek: add RTL8367S-VB Mieczyslaw Nalewaj
2026-11-02 14:37 ` [PATCH net-next v7 02/10] net: dsa: realtek: rtl8365mb: add chip family infrastructure Mieczyslaw Nalewaj
2026-11-02 14:38 ` [PATCH net-next v7 03/10] net: dsa: realtek: rtl8365mb: set speed for family D Mieczyslaw Nalewaj
2026-11-04 12:20 ` Alvin Šipraga
2026-11-02 14:39 ` [PATCH net-next v7 04/10] net: dsa: realtek: rtl8365mb: set RGMII mode " Mieczyslaw Nalewaj
2026-11-04 12:39 ` Alvin Šipraga
2026-11-05 7:56 ` Mieczyslaw Nalewaj
2026-11-05 12:39 ` Alvin Šipraga
2026-11-05 15:27 ` Mieczyslaw Nalewaj
2026-11-06 13:50 ` Alvin Šipraga
2026-11-06 14:56 ` Mieczyslaw Nalewaj
2026-11-06 15:15 ` Alvin Šipraga
2026-11-06 16:43 ` Mieczyslaw Nalewaj [this message]
2026-11-06 15:11 ` Mieczyslaw Nalewaj
2026-11-02 14:40 ` [PATCH net-next v7 05/10] net: dsa: realtek: rtl8365mb: set and get vlan 4k " Mieczyslaw Nalewaj
2026-11-04 12:45 ` Alvin Šipraga
2026-11-02 14:41 ` [PATCH net-next v7 06/10] net: dsa: realtek: rtl8365mb: use raw VID for PVID on " Mieczyslaw Nalewaj
2026-11-02 14:42 ` [PATCH net-next v7 07/10] net: dsa: realtek: rtl8365mb: add family D SDS13 PCS support Mieczyslaw Nalewaj
2026-11-02 14:43 ` [PATCH net-next v7 08/10] net: dsa: realtek: rtl8365mb: re-latch the family D SerDes Mieczyslaw Nalewaj
2026-11-04 12:57 ` Alvin Šipraga
2026-11-05 7:18 ` Mieczyslaw Nalewaj
2026-11-05 8:52 ` Alvin Šipraga
2026-11-05 10:24 ` Mieczyslaw Nalewaj
2026-11-05 12:09 ` Alvin Šipraga
2026-11-06 14:28 ` Alvin Šipraga
2026-11-06 14:56 ` Mieczyslaw Nalewaj
2026-11-06 15:46 ` Alvin Šipraga
2026-11-06 15:49 ` Andrew Lunn
2026-11-02 14:44 ` [PATCH net-next v7 09/10] net: dsa: realtek: rtl8365mb: make L2/LUT access work on family D Mieczyslaw Nalewaj
2026-11-03 15:36 ` Alvin Šipraga
2026-11-03 16:44 ` Mieczyslaw Nalewaj
2026-11-02 14:45 ` [PATCH net-next v7 10/10] net: dsa: realtek: rtl8365mb: add support for RTL8367S-VB Mieczyslaw Nalewaj
2026-11-03 22:52 ` Alvin Šipraga
2026-11-03 23:41 ` Mieczyslaw Nalewaj
2026-11-04 9:40 ` Mieczyslaw Nalewaj
2026-11-04 13:14 ` Alvin Šipraga
2026-11-04 16:37 ` Mieczyslaw Nalewaj
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=29bfb266-8bd4-4c59-868a-cc27259c1f16@yahoo.com \
--to=namiltd@yahoo.com \
--cc=alvin.sipraga@analog.com \
--cc=andrew@lunn.ch \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®