From: Andrew Lunn <andrew@lunn.ch>
To: Artem Novak <artem122novak@gmail.com>
Cc: Steve Glendinning <steve.glendinning@shawell.net>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexandru Tachici <alexandru.tachici@analog.com>,
Andre Edich <andre.edich@microchip.com>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH net 2/2] net: usb: smsc95xx: propagate MDIO write errors
Date: Sat, 14 Nov 2026 23:10:23 +0100 [thread overview]
Message-ID: <8513f7d0-eab3-4288-a097-ecb4e6c69ee2@lunn.ch> (raw)
In-Reply-To: <20261114050954.275495-3-artem122novak@gmail.com>
> Return the error from the helper and propagate it through the
> MDIO bus callback. Continue treating -ENODEV as success during
> device disconnect, consistent with the MDIO read path.
This is logically two different things, so should be two patches.
> Fixes: 05b35e7eb9a1 ("smsc95xx: add phylib support")
net-next.
Andrew
next prev parent reply other threads:[~2026-11-14 22:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 5:09 [PATCH net 0/2] net: usb: smsc95xx: propagate MDIO errors Artem Novak
2026-11-14 5:09 ` [PATCH net 1/2] net: usb: smsc95xx: propagate MDIO reset errors Artem Novak
2026-11-14 22:08 ` Andrew Lunn
2026-11-14 22:12 ` Artem Novak
2026-11-15 5:10 ` sashiko-bot
2026-11-15 5:21 ` netdev-bot+sashiko
2026-11-14 5:09 ` [PATCH net 2/2] net: usb: smsc95xx: propagate MDIO write errors Artem Novak
2026-11-14 22:10 ` Andrew Lunn [this message]
2026-11-14 22:13 ` Artem Novak
2026-11-15 5:10 ` sashiko-bot
2026-11-15 5:21 ` netdev-bot+sashiko
2026-11-14 5:12 ` [PATCH net 0/2] net: usb: smsc95xx: propagate MDIO errors netdev-bot+sinfo
2026-11-14 5:18 ` Artem Novak
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=8513f7d0-eab3-4288-a097-ecb4e6c69ee2@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandru.tachici@analog.com \
--cc=andre.edich@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=artem122novak@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steve.glendinning@shawell.net \
/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.