Re: (subset) [PATCH v3 0/9] NVMEM: Introduce write protection support

[Sascha Hauer <s.hauer@pengutronix.de>]

On Thu, 12 Jun 2025 08:58:03 +0200, Oleksij Rempel wrote:
> This series adds a generic protect op to NVMEM core, enabling
> standardized write protection. This makes NVMEM behave more like other
> flash interfaces (e.g., CFI block protection), which helps with common
> tooling.
> 
> Oleksij Rempel (9):
>   nvmem: Add 'protect' operation to core framework
>   nvmem: rmem: add write and protect support
>   commands: nvmem: Add support for creating dynamic rmem devices
>   regmap: Add reg_seal operation for hardware protection
>   nvmem: regmap: Implement protect operation using regmap_seal
>   nvmem: bsec: Implement NVMEM protect via regmap_seal for OTP locking
>   nvmem: rmem: ensure unique device name per instance
>   fs: Report errors for out-of-bounds protect operations
>   test: Add pytest suite for NVMEM framework
> 
> [...]

Applied, thanks!

[1/9] nvmem: Add 'protect' operation to core framework
      https://git.pengutronix.de/cgit/barebox/commit/?id=485d5d4620a7 (link may not be stable)
[2/9] nvmem: rmem: add write and protect support
      https://git.pengutronix.de/cgit/barebox/commit/?id=bdeaa40c51cd (link may not be stable)
[3/9] commands: nvmem: Add support for creating dynamic rmem devices
      https://git.pengutronix.de/cgit/barebox/commit/?id=f97002b8b0c1 (link may not be stable)
[4/9] regmap: Add reg_seal operation for hardware protection
      https://git.pengutronix.de/cgit/barebox/commit/?id=8f582f13fbce (link may not be stable)
[5/9] nvmem: regmap: Implement protect operation using regmap_seal
      https://git.pengutronix.de/cgit/barebox/commit/?id=94839a59178b (link may not be stable)
[6/9] nvmem: bsec: Implement NVMEM protect via regmap_seal for OTP locking
      https://git.pengutronix.de/cgit/barebox/commit/?id=8e61bcdb871f (link may not be stable)
[7/9] nvmem: rmem: ensure unique device name per instance
      https://git.pengutronix.de/cgit/barebox/commit/?id=5788dad52505 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>