From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v2 0/9] Unify SoC UID and machine hashable data
Date: Mon, 26 Jan 2026 08:56:22 +0100 [thread overview]
Message-ID: <176941418281.174063.16419010478973423369.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251117-soc-uid-v2-0-a2415bf9133d@pengutronix.de>
On Mon, 17 Nov 2025 09:35:33 +0100, Sascha Hauer wrote:
> SoC UID and machine hashable data are both based on the same data but
> are both registered at different places with different functions.
>
> This series aims to unify this by adding a function which uses the
> passed SoC UID to provide it to the environment and also to register
> machine hashable data.
>
> [...]
Applied, thanks!
[1/9] introduce SoC UID
https://git.pengutronix.de/cgit/barebox/commit/?id=c08b9d71cf88 (link may not be stable)
[2/9] soc: imx8mp: Soc ID is 128bit
https://git.pengutronix.de/cgit/barebox/commit/?id=04cd52b05106 (link may not be stable)
[3/9] ARM: i.MX6: print leading zero for SoC ID
https://git.pengutronix.de/cgit/barebox/commit/?id=992e3ab97b95 (link may not be stable)
[4/9] nvmem: bsec: call barebox_set_soc_uid()
https://git.pengutronix.de/cgit/barebox/commit/?id=1a32d891915f (link may not be stable)
[5/9] nvmem: imx-ocotp-ele: call barebox_set_soc_uid()
https://git.pengutronix.de/cgit/barebox/commit/?id=22eb66644d4d (link may not be stable)
[6/9] nvmem: ocotp: Fix SoC ID reading for i.MX8MP
https://git.pengutronix.de/cgit/barebox/commit/?id=27d385ec7ef9 (link may not be stable)
[7/9] nvmem: imx-ocotp: call barebox_set_soc_uid()
https://git.pengutronix.de/cgit/barebox/commit/?id=f2080b0e55bc (link may not be stable)
[8/9] soc: imx8m: register SoC UID
https://git.pengutronix.de/cgit/barebox/commit/?id=966df836f1c9 (link may not be stable)
[9/9] Documentation: migration: add i.MX8MP SoC UID change note
(no commit info)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-01-26 7:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 8:35 Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 1/9] introduce SoC UID Sascha Hauer
2025-11-17 10:16 ` Jonas Rebmann
2025-11-17 11:28 ` Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 2/9] soc: imx8mp: Soc ID is 128bit Sascha Hauer
2025-11-17 9:59 ` Jonas Rebmann
2025-11-17 11:02 ` Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 3/9] ARM: i.MX6: print leading zero for SoC ID Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 4/9] nvmem: bsec: call barebox_set_soc_uid() Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 5/9] nvmem: imx-ocotp-ele: " Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 6/9] nvmem: ocotp: Fix SoC ID reading for i.MX8MP Sascha Hauer
2026-01-26 11:20 ` Ahmad Fatoum
2026-01-27 7:20 ` Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 7/9] nvmem: imx-ocotp: call barebox_set_soc_uid() Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 8/9] soc: imx8m: register SoC UID Sascha Hauer
2025-11-17 8:35 ` [PATCH v2 9/9] Documentation: migration: add i.MX8MP SoC UID change note Sascha Hauer
2026-01-26 7:56 ` 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=176941418281.174063.16419010478973423369.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox