From: Andrew Lunn <andrew@lunn.ch>
To: Sander Vanheule <sander@svanheule.net>
Cc: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support
Date: Sat, 5 Jun 2021 01:55:42 +0200 [thread overview]
Message-ID: <YLq9fgtj1xb0peA+@lunn.ch> (raw)
In-Reply-To: <cover.1622743333.git.sander@svanheule.net>
> I have zero experience with clause-45 devices, and no such devices
> available for testing. As such, clause-45 code in the second patch is
> entirely untested, although it isn't very complex.
Normal kernel policy is not to merge something if it has no users. As
i said in another reply, the only users of regmap-mdio are going to be
Ethernet switch and funky mdio devices. So far, i've not seen a C45
Ethernet switch, nor a funky c45 mdio device. So i suggest we leave it
on the mainline list until some hardware which could use it comes
along.
Andrew
next prev parent reply other threads:[~2021-06-04 23:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 18:25 [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support Sander Vanheule
2021-06-03 18:25 ` [RFC PATCH 1/2] regmap: mdio: Clean up invalid clause-22 addresses Sander Vanheule
2021-06-03 18:25 ` [RFC PATCH 2/2] regmap: mdio: Add clause-45 support Sander Vanheule
2021-06-04 17:25 ` [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support Mark Brown
2021-06-04 18:16 ` Sander Vanheule
2021-06-07 11:54 ` Mark Brown
2021-06-07 12:06 ` Sander Vanheule
2021-06-07 12:14 ` Andy Shevchenko
2021-06-04 20:38 ` Andrew Lunn
2021-06-04 23:55 ` Andrew Lunn [this message]
2021-06-05 8:31 ` [PATCH] regmap: mdio: Reject invalid clause-22 addresses Sander Vanheule
2021-06-07 11:03 ` Mark Brown
2021-06-07 11:12 ` Sander Vanheule
2021-06-09 11:51 ` Sander Vanheule
2021-06-08 16:06 ` [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support Mark Brown
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=YLq9fgtj1xb0peA+@lunn.ch \
--to=andrew@lunn.ch \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sander@svanheule.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).