From: Leo Famulari <leo@famulari.name>
To: 74449@debbugs.gnu.org
Subject: [bug#74449] 2024-11-17 kernel updates
Date: Sun, 24 Nov 2024 13:04:26 -0500 [thread overview]
Message-ID: <Z0NqqmK1PC8-WERu@jasmine.lan> (raw)
In-Reply-To: <Zz5_Gzf4PXuK_caC@jasmine.lan>
[-- Attachment #1.1: Type: text/plain, Size: 350 bytes --]
I pushed the first 6 patches of this series as
c05a78739de9ad2ca2ea97c5899d9b73fca620ea
I've had to amend the commit of the 4.19 kernel series to 4.19.324
because it had the wrong commit hashes. It's building on the
'kernel-updates' branch.
The problem was that I fetched release artifacts for 4.19.234, not
4.19.324. Oops!
Updated patch attached
[-- Attachment #1.2: 0001-gnu-linux-libre-4.19-Update-to-4.19.324.patch --]
[-- Type: text/plain, Size: 1762 bytes --]
From 4931d022b09f03068337c356a4f53e377b50d8e5 Mon Sep 17 00:00:00 2001
Message-ID: <4931d022b09f03068337c356a4f53e377b50d8e5.1732471461.git.leo@famulari.name>
From: Leo Famulari <leo@famulari.name>
Date: Wed, 20 Nov 2024 19:28:54 -0500
Subject: [PATCH] gnu: linux-libre 4.19: Update to 4.19.324.
* gnu/packages/linux.scm (linux-libre-4.19-version): Update to 4.19.324.
(linux-libre-4.19-pristine-source): Update hash.
Change-Id: I82e9d32dc7adbeaa9e416c3a2dd4763d8cb28c3c
---
gnu/packages/linux.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 0e29aae2bd..3583da37c2 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -606,7 +606,7 @@ (define-public linux-libre-5.4-pristine-source
(%upstream-linux-source version hash)
deblob-scripts-5.4)))
-(define-public linux-libre-4.19-version "4.19.323")
+(define-public linux-libre-4.19-version "4.19.324")
(define-public linux-libre-4.19-gnu-revision "gnu1")
(define deblob-scripts-4.19
(linux-libre-deblob-scripts
@@ -616,7 +616,7 @@ (define deblob-scripts-4.19
(base32 "048isws4h3lya8dwpwyhqglsjg9sckxk0gfsxdbqg336n5vi0gb1")))
(define-public linux-libre-4.19-pristine-source
(let ((version linux-libre-4.19-version)
- (hash (base32 "073akfd30bnk0r8hw1lywv2d7svslhfl5lx9zlkdhjf6p9gj3jgf")))
+ (hash (base32 "1rpzhx6zx7kav638m78fcqhw3igzggdcyc2r7ns8inh75nnl1qch")))
(make-linux-libre-source version
(%upstream-linux-source version hash)
deblob-scripts-4.19)))
base-commit: c05a78739de9ad2ca2ea97c5899d9b73fca620ea
--
2.46.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-24 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 0:30 [bug#74449] 2024-11-17 kernel updates Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 1/7] gnu: linux-libre: Update to 6.11.9 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.62 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.118 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.173 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.230 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.286 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.324 Leo Famulari
2024-11-24 18:04 ` Leo Famulari [this message]
2024-11-24 23:36 ` bug#74449: 2024-11-17 kernel updates Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z0NqqmK1PC8-WERu@jasmine.lan \
--to=leo@famulari.name \
--cc=74449@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).