From: Fabio Estevam <festevam@gmail.com>
To: trini@konsulko.com
Cc: u-boot@lists.denx.de
Subject: [GIT PULL] Please pull u-boot-imx-master-20240317
Date: Sun, 17 Mar 2024 20:34:20 -0300 [thread overview]
Message-ID: <20240317233420.330902-1-festevam@gmail.com> (raw)
Hi Tom,
Please pull these fixes from u-boot-imx, thanks.
The following changes since commit 86fd291a7990af84e96808f48eff2219dd4ef496:
Merge tag 'efi-2024-04-rc5' of https://source.denx.de/u-boot/custodians/u-boot-efi (2024-03-13 20:39:46 -0400)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-imx.git tags/u-boot-imx-master-20240317
for you to fetch changes up to e648c4a3455a4d1880efe121602ed90a0bc9b53f:
arm: imx: imx8m: soc: Fix NPU/VPU fdt disable fixup (2024-03-17 18:00:04 -0300)
u-boot-imx-master-20240317
--------------------------
CI: https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/19974
- Fix build error when SoM detection on Phytec board.
- Fix sc_misc_otp_fuse_read() error check on colibri-imx8x/apalis-imx8.
- Fix NPU/VPU fdt disable fixup on i.MX8M.
----------------------------------------------------------------
Benjamin Hahn (1):
board: phytec: define get_som_type also when SoM detection is disabled
Fabio Estevam (2):
colibri-imx8x: Fix sc_misc_otp_fuse_read() error check
apalis-imx8: Fix sc_misc_otp_fuse_read() error check
Vitor Soares (1):
arm: imx: imx8m: soc: Fix NPU/VPU fdt disable fixup
arch/arm/mach-imx/imx8m/soc.c | 18 ++++++++++++++----
board/phytec/common/phytec_som_detection.c | 5 +++++
board/toradex/apalis-imx8/apalis-imx8.c | 2 +-
board/toradex/colibri-imx8x/colibri-imx8x.c | 2 +-
4 files changed, 21 insertions(+), 6 deletions(-)
next reply other threads:[~2024-03-17 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 23:34 Fabio Estevam [this message]
2024-03-18 12:27 ` [GIT PULL] Please pull u-boot-imx-master-20240317 Tom Rini
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=20240317233420.330902-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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