From: Andrew Lunn <andrew@lunn.ch>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Catalin Popescu <catalin.popescu@leica-geosystems.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] net: phy: dp83826: Add support for straps reading
Date: Mon, 3 Mar 2025 18:20:47 +0100 [thread overview]
Message-ID: <fcc25495-5453-4b15-aece-b01bca3a00ba@lunn.ch> (raw)
In-Reply-To: <20250303-dp83826-fixes-v1-2-6901a04f262d@yoseli.org>
On Mon, Mar 03, 2025 at 06:05:52PM +0100, Jean-Michel Hautbois wrote:
> When the DP83826 is probed, read the straps, and apply the default
> settings expected. The MDI-X is not yet supported, but still read the
> strap.
What about backwards compatibility? I expect this changes the
behaviour of the device, potentially introducing regressions? Please
add an explanation of why this is safe.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2025-03-03 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 17:05 [PATCH 0/2] net: phy: dp83826: Enable strap reading and fix TX data voltage support Jean-Michel Hautbois
2025-03-03 17:05 ` [PATCH 1/2] net: phy: dp83826: Fix " Jean-Michel Hautbois
2025-03-14 9:00 ` Jean-Michel Hautbois
2025-03-03 17:05 ` [PATCH 2/2] net: phy: dp83826: Add support for straps reading Jean-Michel Hautbois
2025-03-03 17:20 ` Andrew Lunn [this message]
2025-03-03 17:37 ` Jean-Michel Hautbois
2025-03-03 17:50 ` Andrew Lunn
2025-03-03 17:53 ` Jean-Michel Hautbois
2025-03-04 6:37 ` Jean-Michel Hautbois
2025-03-03 17:25 ` Russell King (Oracle)
2025-03-03 17:35 ` Jean-Michel Hautbois
2025-03-03 18:08 ` Russell King (Oracle)
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=fcc25495-5453-4b15-aece-b01bca3a00ba@lunn.ch \
--to=andrew@lunn.ch \
--cc=catalin.popescu@leica-geosystems.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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®