linux-kernel - Re: [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue,  8 Jun 2021 17:06:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Andrew Lunn <andrew@...n.ch>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Sander Vanheule <sander@...nheule.net>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support

On Thu, 3 Jun 2021 20:25:08 +0200, Sander Vanheule wrote:
> The initial MDIO regmap implementation only supported (or claimed to
> only support) clause-22 register access, with 5 bit register addresses.
> However, this was not enforced sufficiently, and regnum values were
> passed verbatim to the mdio bus subsystem.
> 
> These patches aim to enforce the register address width, and also add
> clause-45 support for extended address spaces. A clause-45 address is
> defined here as the composite of the device type (see MDIO_MMD_* in
> include/uapi/linux/mdio.h) and the register number, for a total width of
> 21 bit.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/2] regmap: mdio: Clean up invalid clause-22 addresses
      commit: dff404deb8493e6154ad75a62ce7c4e37ff8fccd
[2/2] regmap: mdio: Add clause-45 support
      commit: f083be9db060fbac09123d80bdffb2c001ac0e2b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark