From: Roberto Medina <robertoxmed@gmail.com>
To: buildroot@buildroot.org
Cc: Roberto Medina <robertoxmed@gmail.com>
Subject: [Buildroot] [PATCH v2 0/1] configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A
Date: Fri, 25 Oct 2024 10:32:47 +0100 [thread overview]
Message-ID: <20241025093248.2015508-1-robertoxmed@gmail.com> (raw)
v2 -> v1:
- Enable checking hashes and add relevant hash files.
- Move from Glibc to uClibc.
Roberto Medina (1):
configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A
.../arm-trusted-firmware/arm-trusted-firmware.hash | 2 ++
.../patches/linux-headers/linux-headers.hash | 1 +
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 | 11 +++++++----
5 files changed, 14 insertions(+), 4 deletions(-)
create mode 100644 board/firefly/roc-rk3399-pc/patches/arm-trusted-firmware/arm-trusted-firmware.hash
create mode 120000 board/firefly/roc-rk3399-pc/patches/linux-headers/linux-headers.hash
create mode 100644 board/firefly/roc-rk3399-pc/patches/linux/linux.hash
create mode 100644 board/firefly/roc-rk3399-pc/patches/uboot/uboot.hash
--
2.47.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-10-25 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 9:32 Roberto Medina [this message]
2024-10-25 9:32 ` [Buildroot] [PATCH v2 1/1] configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A Roberto Medina
2024-11-04 22:12 ` Julien Olivain
2024-11-04 22:14 ` Thomas Petazzoni via buildroot
2024-11-17 22:05 ` Roberto Medina
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=20241025093248.2015508-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.