From: Roberto Medina <robertoxmed@gmail.com>
To: buildroot@buildroot.org
Cc: Roberto Medina <robertoxmed@gmail.com>
Subject: [Buildroot] [PATCH 0/1] config/roc_pc_rk3399: Bump Linux, TF-A, U-Boot
Date: Mon, 16 Mar 2026 22:36:46 +0100 [thread overview]
Message-ID: <20260316213647.6721-1-robertoxmed@gmail.com> (raw)
Taking the opportunity to refresh the configuration of this board.
The CI [1] notified me that U-Boot is no longer building for the version
that was being used for the board.
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/13492838038
Roberto Medina (1):
configs/roc_pc_rk3399: Bump Linux, TF-A, U-Boot
.../arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
board/firefly/roc-rk3399-pc/patches/linux/linux.hash | 2 +-
board/firefly/roc-rk3399-pc/patches/uboot/uboot.hash | 2 +-
configs/roc_pc_rk3399_defconfig | 9 +++++----
4 files changed, 8 insertions(+), 7 deletions(-)
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-16 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 21:36 Roberto Medina [this message]
2026-03-16 21:36 ` [Buildroot] [PATCH 1/1] configs/roc_pc_rk3399: Bump Linux, TF-A, U-Boot Roberto Medina
2026-03-18 12:22 ` Julien Olivain via buildroot
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=20260316213647.6721-1-robertoxmed@gmail.com \
--to=robertoxmed@gmail.com \
--cc=buildroot@buildroot.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