From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] package/rpi-firmware: bump version to 62a0d75
Date: Tue, 14 Jan 2020 17:36:53 +0100 [thread overview]
Message-ID: <20200114163653.GE22540@scaer> (raw)
In-Reply-To: <20200114094256.23174-2-ps.report@gmx.net>
Peter, All,
On 2020-01-14 10:42 +0100, Peter Seiderer spake thusly:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/rpi-firmware/rpi-firmware.hash | 2 +-
> package/rpi-firmware/rpi-firmware.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
> index 63d8ac50a0..b5bb4d9f37 100644
> --- a/package/rpi-firmware/rpi-firmware.hash
> +++ b/package/rpi-firmware/rpi-firmware.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 b3c5c9d3cda1f77caf317b8d1f0496cd7ca791ddaeec8207a5a1940111483509 rpi-firmware-1.20190925.tar.gz
> +sha256 088d094618924a90f65bb511808bbeb921e0769c878fa7baa9626954206f61a2 rpi-firmware-62a0d75b67484cb306a2a6f8fa954d9644868169.tar.gz
> sha256 ba76edfc10a248166d965b8eaf320771c44f4f432d4fce2fd31fd272e7038add boot/LICENCE.broadcom
> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
> index ee59ee2f26..b320e11233 100644
> --- a/package/rpi-firmware/rpi-firmware.mk
> +++ b/package/rpi-firmware/rpi-firmware.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -RPI_FIRMWARE_VERSION = 1.20190925
> +RPI_FIRMWARE_VERSION = 62a0d75b67484cb306a2a6f8fa954d9644868169
This goes from a tag to a sha1. Why do we need to do so? This should be
explained in the commit log.
Regards,
Yann E. MORIN.
> RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
> RPI_FIRMWARE_LICENSE = BSD-3-Clause
> RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
> --
> 2.24.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-01-14 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:42 [Buildroot] [PATCH v1 1/3] configs/raspberrypi*: bump kernel version to 301ec88 Peter Seiderer
2020-01-14 9:42 ` [Buildroot] [PATCH v1 2/3] package/rpi-firmware: bump version to 62a0d75 Peter Seiderer
2020-01-14 16:36 ` Yann E. MORIN [this message]
2020-01-14 17:29 ` Peter Seiderer
2020-01-14 19:44 ` Martin Bark
2020-01-15 20:55 ` Peter Seiderer
2020-01-14 9:42 ` [Buildroot] [PATCH v1 3/3] package/rpi-userland: bump version to 42ec119 Peter Seiderer
2020-01-14 12:45 ` daggs
2020-01-14 14:27 ` Peter Seiderer
2020-01-14 16:32 ` Yann E. MORIN
2020-01-14 17:19 ` Peter Seiderer
2020-01-14 20:20 ` Thomas Petazzoni
2020-01-14 21:17 ` daggs
2020-01-15 20:57 ` Peter Seiderer
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=20200114163653.GE22540@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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