From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/3] net: phy: micrel: Code clean-up
Date: Fri, 15 May 2026 16:50:23 +0200 [thread overview]
Message-ID: <cover.1778856199.git.christophe.jaillet@wanadoo.fr> (raw)
This serie is only some clean-up related to
drivers/net/mdio/mdio-mscc-miim.c
It depends on a patch called "[PATCH net-next] net: phy: micrel: use dev_err_probe()"
that has been sent recently.
Note that in the 2nd patch, the order of the calls in the remove
function is changed. I don't think that it matters, but I'm always
relunctent to change such things.
The patches are compile tested only.
Christophe JAILLET (3):
net: mdio: mscc-miim: Remove some redundant code
net: mdio: mscc-miim: Use devm_clk_get_optional_enabled()
net: mdio: mscc-miim: Use devm_of_mdiobus_register()
drivers/net/mdio/mdio-mscc-miim.c | 34 +++++--------------------------
1 file changed, 5 insertions(+), 29 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-15 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 14:50 Christophe JAILLET [this message]
2026-05-15 14:50 ` [PATCH 1/3 net-next] net: mdio: mscc-miim: Remove some redundant code Christophe JAILLET
2026-05-15 15:45 ` Maxime Chevallier
2026-05-15 14:50 ` [PATCH 2/3 net-next] net: mdio: mscc-miim: Use devm_clk_get_optional_enabled() Christophe JAILLET
2026-05-15 15:53 ` Maxime Chevallier
2026-05-15 14:50 ` [PATCH 3/3 net-next] net: mdio: mscc-miim: Use devm_of_mdiobus_register() Christophe JAILLET
2026-05-15 15:54 ` Maxime Chevallier
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=cover.1778856199.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel-janitors@vger.kernel.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 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.