* [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211
@ 2024-01-09 18:33 Jan Čermák
2024-01-14 9:06 ` Yann E. MORIN
0 siblings, 1 reply; 5+ messages in thread
From: Jan Čermák @ 2024-01-09 18:33 UTC (permalink / raw)
To: buildroot; +Cc: Jan Čermák, Bernd Kuhls, Yann E. MORIN
Updated WHENCE hash due to various commits:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
Signed-off-by: Jan Čermák <sairon@sairon.cz>
---
package/linux-firmware/linux-firmware.hash | 4 ++--
package/linux-firmware/linux-firmware.mk | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/linux-firmware/linux-firmware.hash b/package/linux-firmware/linux-firmware.hash
index 6722aa14c6..4b188032bf 100644
--- a/package/linux-firmware/linux-firmware.hash
+++ b/package/linux-firmware/linux-firmware.hash
@@ -1,5 +1,5 @@
# From https://mirrors.edge.kernel.org/pub/linux/kernel/firmware/sha256sums.asc
-sha256 c98d200fc4a3120de1a594713ce34e135819dff23e883a4ed387863ba25679c7 linux-firmware-20231030.tar.xz
+sha256 96af7e4b5eabd37869cdb3dcbb7ab36911106d39b76e799fa1caab16a9dbe8bb linux-firmware-20231211.tar.xz
# Hash for license files
sha256 8116433f4004fc0c24d72b3d9e497808b724aa0e5e1cd63fc1bf66b715b1e2e9 LICENCE.Abilis
@@ -36,6 +36,6 @@ sha256 8542aeabf2761935122d693561e16766ce1bcc2b0d003204f9040b7d6d929f2e LICENS
sha256 be904cd28cb292b80cdb6cf412ab0d9159d431671e987ad433c1f62e0988a9bc LICENSE.qcom
sha256 fc6223d4bfe9f2f9e2eddc44b9fe5721d0caf49f01cb08d602906add686d8c6f LICENSE.radeon
sha256 2bdd2e716f05d9737d3f9a20f9a3a3c0caee0e866100ddb0673f1178e42f92b9 LICENSE.sdma_firmware
-sha256 697134859b663bc110d57275a7a7862bba21c4425266aac8c62bee18202aac20 WHENCE
+sha256 dd63e67d3d9e51f84fed9a3efa7a465310b5b5058969eb7295a58339227aee14 WHENCE
sha256 fa43e1b9a13b341a07adca9dbe73d0f9072d7966fdfe811c01f0dd2872d7309a qcom/NOTICE.txt
sha256 bef9c828e84f21e7835b4de7daf954a327e1ff777871b58e116039b684c0d604 LICENCE.e100
diff --git a/package/linux-firmware/linux-firmware.mk b/package/linux-firmware/linux-firmware.mk
index 96905dd909..ffb4fc2e7b 100644
--- a/package/linux-firmware/linux-firmware.mk
+++ b/package/linux-firmware/linux-firmware.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LINUX_FIRMWARE_VERSION = 20231030
+LINUX_FIRMWARE_VERSION = 20231211
LINUX_FIRMWARE_SOURCE = linux-firmware-$(LINUX_FIRMWARE_VERSION).tar.xz
LINUX_FIRMWARE_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/firmware
LINUX_FIRMWARE_INSTALL_IMAGES = YES
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211
2024-01-09 18:33 [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211 Jan Čermák
@ 2024-01-14 9:06 ` Yann E. MORIN
2024-01-17 11:15 ` Jan Čermák
0 siblings, 1 reply; 5+ messages in thread
From: Yann E. MORIN @ 2024-01-14 9:06 UTC (permalink / raw)
To: Jan Čermák; +Cc: Bernd Kuhls, buildroot
Jan, All,
On 2024-01-09 19:33 +0100, Jan Čermák spake thusly:
> Updated WHENCE hash due to various commits:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
If the file changed, that is because there were changes upstream, so
stating there are "various commits" that changed the file is not very
helpful.
What the hashes for license files are for, is to be able to detect
changes in licensing terms, i.e. whether we need to update our _LICENSE
entries. So anty change in the license file needs to be analysed in that
regard.
For linux-firmware, WHENCE is just a huge list of all files and their
associated license files; thus it mostly grows new entriesr. The
existing entries never change; when they do, it's mostly typoes.
So, a better phrasing would have been:
Updated WHENCE hash due to various new entries for new blobs.
(which I forgot to do when applying, so I guess I need to go and grab
another coffee. ;-) )
> Signed-off-by: Jan Čermák <sairon@sairon.cz>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/linux-firmware/linux-firmware.hash | 4 ++--
> package/linux-firmware/linux-firmware.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/linux-firmware/linux-firmware.hash b/package/linux-firmware/linux-firmware.hash
> index 6722aa14c6..4b188032bf 100644
> --- a/package/linux-firmware/linux-firmware.hash
> +++ b/package/linux-firmware/linux-firmware.hash
> @@ -1,5 +1,5 @@
> # From https://mirrors.edge.kernel.org/pub/linux/kernel/firmware/sha256sums.asc
> -sha256 c98d200fc4a3120de1a594713ce34e135819dff23e883a4ed387863ba25679c7 linux-firmware-20231030.tar.xz
> +sha256 96af7e4b5eabd37869cdb3dcbb7ab36911106d39b76e799fa1caab16a9dbe8bb linux-firmware-20231211.tar.xz
>
> # Hash for license files
> sha256 8116433f4004fc0c24d72b3d9e497808b724aa0e5e1cd63fc1bf66b715b1e2e9 LICENCE.Abilis
> @@ -36,6 +36,6 @@ sha256 8542aeabf2761935122d693561e16766ce1bcc2b0d003204f9040b7d6d929f2e LICENS
> sha256 be904cd28cb292b80cdb6cf412ab0d9159d431671e987ad433c1f62e0988a9bc LICENSE.qcom
> sha256 fc6223d4bfe9f2f9e2eddc44b9fe5721d0caf49f01cb08d602906add686d8c6f LICENSE.radeon
> sha256 2bdd2e716f05d9737d3f9a20f9a3a3c0caee0e866100ddb0673f1178e42f92b9 LICENSE.sdma_firmware
> -sha256 697134859b663bc110d57275a7a7862bba21c4425266aac8c62bee18202aac20 WHENCE
> +sha256 dd63e67d3d9e51f84fed9a3efa7a465310b5b5058969eb7295a58339227aee14 WHENCE
> sha256 fa43e1b9a13b341a07adca9dbe73d0f9072d7966fdfe811c01f0dd2872d7309a qcom/NOTICE.txt
> sha256 bef9c828e84f21e7835b4de7daf954a327e1ff777871b58e116039b684c0d604 LICENCE.e100
> diff --git a/package/linux-firmware/linux-firmware.mk b/package/linux-firmware/linux-firmware.mk
> index 96905dd909..ffb4fc2e7b 100644
> --- a/package/linux-firmware/linux-firmware.mk
> +++ b/package/linux-firmware/linux-firmware.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -LINUX_FIRMWARE_VERSION = 20231030
> +LINUX_FIRMWARE_VERSION = 20231211
> LINUX_FIRMWARE_SOURCE = linux-firmware-$(LINUX_FIRMWARE_VERSION).tar.xz
> LINUX_FIRMWARE_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/firmware
> LINUX_FIRMWARE_INSTALL_IMAGES = YES
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211
2024-01-14 9:06 ` Yann E. MORIN
@ 2024-01-17 11:15 ` Jan Čermák
2024-01-19 20:44 ` Yann E. MORIN
0 siblings, 1 reply; 5+ messages in thread
From: Jan Čermák @ 2024-01-17 11:15 UTC (permalink / raw)
To: Yann E. MORIN; +Cc: Bernd Kuhls, buildroot
Hi Yann,
>> Updated WHENCE hash due to various commits:
>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
>
> If the file changed, that is because there were changes upstream, so
> stating there are "various commits" that changed the file is not very
> helpful.
It's a bit vague formulation indeed, however it's accompanied with the
link to the list of changes in the upstream git tree. Unfortunately cgit
UI doesn't have a way to specify commit range to limit the list of commits.
Anyway, I simply followed the example of previous updates of
linux-firmware, where a similar wording was used:
----
commit f9ff92a0793fe86353583fc5d36e74ef7e79c255
Author: Bernd Kuhls <bernd@kuhls.net>
Date: Fri Nov 3 21:11:31 2023 +0100
package/linux-firmware: bump version to 20231030
Updated license hash due to various commits:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
---
commit f9ff92a0793fe86353583fc5d36e74ef7e79c255
Author: Bernd Kuhls <bernd@kuhls.net>
Date: Fri Nov 3 21:11:31 2023 +0100
package/linux-firmware: bump version to 20231030
Updated license hash due to various commits:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
---
In some cases the hash was updated without any log message at all, like
in bec9e5f7852f6fefb234877dff45916d921c4b18.
But no problem, I don't take it personally. Seeing you addressed "all"
in your reply, I get it's something that we should all be more careful
about :)
> So, a better phrasing would have been:
>
> Updated WHENCE hash due to various new entries for new blobs.
>
I'll try to keep it in mind for the next time, thanks.
Cheers,
Jan
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211
2024-01-17 11:15 ` Jan Čermák
@ 2024-01-19 20:44 ` Yann E. MORIN
0 siblings, 0 replies; 5+ messages in thread
From: Yann E. MORIN @ 2024-01-19 20:44 UTC (permalink / raw)
To: Jan Čermák; +Cc: Bernd Kuhls, buildroot
Jan, All,
On 2024-01-17 12:15 +0100, Jan Čermák spake thusly:
> > > Updated WHENCE hash due to various commits:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
> >
> > If the file changed, that is because there were changes upstream, so
> > stating there are "various commits" that changed the file is not very
> > helpful.
> It's a bit vague formulation indeed, however it's accompanied with the link
> to the list of changes in the upstream git tree. Unfortunately cgit UI
> doesn't have a way to specify commit range to limit the list of commits.
> Anyway, I simply followed the example of previous updates of linux-firmware,
> where a similar wording was used:
Right, and that's nice that you looked at previous entries, thanks! :-)
Improving the commit logs is also a long-lasting goal and effort of
mine, one commit at a time! ;-)
Thank you for your contributions!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <20240109183354.361126-1-sairon__40282.8532781982$1704825264$gmane$org@sairon.cz>]
end of thread, other threads:[~2024-01-19 20:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-01-09 18:33 [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211 Jan Čermák
2024-01-14 9:06 ` Yann E. MORIN
2024-01-17 11:15 ` Jan Čermák
2024-01-19 20:44 ` Yann E. MORIN
[not found] <20240109183354.361126-1-sairon__40282.8532781982$1704825264$gmane$org@sairon.cz>
2024-01-13 21:40 ` Bernd Kuhls
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox