From: Sander Vanheule <sander@svanheule.net>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Adrew Lunn <andrew@lunn.ch>,
Sander Vanheule <sander@svanheule.net>
Subject: [PATCH 0/2] Clause-22/Clause-45 MDIO regmap support fixups
Date: Wed, 9 Jun 2021 13:46:04 +0200 [thread overview]
Message-ID: <cover.1623238313.git.sander@svanheule.net> (raw)
A proposed patch to make C22 access more strict [1], was posted in reply to an
RFC series which also added C45 register access [2]. It appears that as a
result, the original RFC patches got merged instead.
Since there are currently no (planned) C45 regmap users, this patch is
reverted. C22 access functions are corrected to return -ENXIO, instead of
silently ignoring any invalid high bits in the register offset.
[1] Proposed C22 patch:
https://lore.kernel.org/lkml/20210605083116.12786-1-sander@svanheule.net/
[2] RFC series:
https://lore.kernel.org/lkml/cover.1622743333.git.sander@svanheule.net/
Sander Vanheule (2):
Revert "regmap: mdio: Add clause-45 support"
regmap: mdio: Reject invalid clause-22 addresses
drivers/base/regmap/regmap-mdio.c | 72 ++++++++-----------------------
1 file changed, 18 insertions(+), 54 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-09 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 11:46 Sander Vanheule [this message]
2021-06-09 11:46 ` [PATCH 1/2] Revert "regmap: mdio: Add clause-45 support" Sander Vanheule
2021-06-09 12:24 ` Mark Brown
2021-06-09 12:42 ` Sander Vanheule
2021-06-09 13:23 ` Mark Brown
2021-06-09 11:46 ` [PATCH 2/2] regmap: mdio: Reject invalid clause-22 addresses Sander Vanheule
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.1623238313.git.sander@svanheule.net \
--to=sander@svanheule.net \
--cc=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 \
/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.