From: Andrew Lunn <andrew@lunn.ch>
To: Liu Changjie <liucj1228@outlook.com>
Cc: Heiner Kallweit <hkallweit1@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, Russell King <linux@armlinux.org.uk>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: Add Maxio MAE0621A support
Date: Thu, 16 Jul 2026 18:32:33 +0200 [thread overview]
Message-ID: <c29b6b04-6cf3-4f7f-8be1-160346ef746b@lunn.ch> (raw)
In-Reply-To: <MN0PR19MB609111152E1C759EC7F13DC6ACC72@MN0PR19MB6091.namprd19.prod.outlook.com>
On Fri, Jul 17, 2026 at 12:14:17AM +0800, Liu Changjie wrote:
> Hi Andrew,
>
> > What happens when 100Mbps or 10Mbps is negotiated? Has that been
> > tested?
>
> Thanks for asking. I had only exercised 1 Gbit/s before sending this
> series.
>
> I have now repeated the test with autonegotiation enabled on both ends,
> restricting the link partner advertisement to one full-duplex mode at a
> time.
Thanks for the extensive testing. There is no need to give the details
in the commit message, just make the current comment indicate that all
link modes have been tested.
Andrew
prev parent reply other threads:[~2026-07-16 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 6:46 [PATCH net-next 0/2] net: phy: Add Maxio MAE0621A support Liu Changjie
2026-07-14 21:29 ` Andrew Lunn
2026-07-16 16:14 ` Liu Changjie
2026-07-16 16:32 ` Andrew Lunn [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=c29b6b04-6cf3-4f7f-8be1-160346ef746b@lunn.ch \
--to=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liucj1228@outlook.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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