mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH v3 0/9] NVMEM: Introduce write protection support
Date: Mon, 23 Jun 2025 13:59:40 +0200	[thread overview]
Message-ID: <175067998077.3057263.7997684573569433171.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250612065812.2025665-1-o.rempel@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=48f82c055d52 (link may not be stable)
[2/9] nvmem: rmem: add write and protect support
      https://git.pengutronix.de/cgit/barebox/commit/?id=84f53d52bd70 (link may not be stable)
[3/9] commands: nvmem: Add support for creating dynamic rmem devices
      https://git.pengutronix.de/cgit/barebox/commit/?id=d1543b907b46 (link may not be stable)
[4/9] regmap: Add reg_seal operation for hardware protection
      https://git.pengutronix.de/cgit/barebox/commit/?id=b0eae07039c0 (link may not be stable)
[5/9] nvmem: regmap: Implement protect operation using regmap_seal
      https://git.pengutronix.de/cgit/barebox/commit/?id=c324f39e5914 (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=f4e69880442d (link may not be stable)
[7/9] nvmem: rmem: ensure unique device name per instance
      https://git.pengutronix.de/cgit/barebox/commit/?id=5450d627c760 (link may not be stable)
[8/9] fs: Report errors for out-of-bounds protect operations
      https://git.pengutronix.de/cgit/barebox/commit/?id=54698cced077 (link may not be stable)
[9/9] test: Add pytest suite for NVMEM framework
      https://git.pengutronix.de/cgit/barebox/commit/?id=85e0492d19dc (link may not be stable)

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




      parent reply	other threads:[~2025-06-23 13:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  6:58 Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 1/9] nvmem: Add 'protect' operation to core framework Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 2/9] nvmem: rmem: add write and protect support Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 3/9] commands: nvmem: Add support for creating dynamic rmem devices Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 4/9] regmap: Add reg_seal operation for hardware protection Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 5/9] nvmem: regmap: Implement protect operation using regmap_seal Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 6/9] nvmem: bsec: Implement NVMEM protect via regmap_seal for OTP locking Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 7/9] nvmem: rmem: ensure unique device name per instance Oleksij Rempel
2025-06-12  6:58 ` [PATCH v3 8/9] fs: Report errors for out-of-bounds protect operations Oleksij Rempel
2025-06-17  7:56   ` Sascha Hauer
2025-06-25  5:45     ` Ahmad Fatoum
2025-06-25  7:11       ` Sascha Hauer
2025-06-12  6:58 ` [PATCH v3 9/9] test: Add pytest suite for NVMEM framework Oleksij Rempel
2025-06-17  8:03   ` Sascha Hauer
2025-06-17  8:17     ` Oleksij Rempel
2025-06-17  8:04 ` (subset) [PATCH v3 0/9] NVMEM: Introduce write protection support Sascha Hauer
2025-06-23 11:59 ` Sascha Hauer [this message]

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=175067998077.3057263.7997684573569433171.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=o.rempel@pengutronix.de \
    /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