From: Elias Pukari <elias.pukari@gmail.com>
To: netdev-bot+sashiko@kernel.org
Cc: Elias Pukari <elias.pukari@gmail.com>,
netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: phy: et1011c: don't write an error code to the config register
Date: Wed, 18 Nov 2026 17:05:30 +0200 [thread overview]
Message-ID: <20261118150530.16472-1-elias.pukari@gmail.com> (raw)
In-Reply-To: <179485554872.3136.2853572906945647083@kernel.org>
On v2, an injected MDIO read error put the PHY in PHY_ERROR, and a
restart at the same speed skipped the configuration write. I'll send v3
to cache the speed only after configuration succeeds.
pw-bot: cr
prev parent reply other threads:[~2026-11-18 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 18:07 Elias Pukari
2026-11-15 18:24 ` Andrew Lunn
2026-11-16 18:59 ` netdev-bot+sashiko
2026-11-18 15:05 ` Elias Pukari [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=20261118150530.16472-1-elias.pukari@gmail.com \
--to=elias.pukari@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev-bot+sashiko@kernel.org \
--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®