From: Leo Famulari <leo@famulari.name>
To: 67840@debbugs.gnu.org
Cc: w@wmeyer.eu, Leo Famulari <leo@famulari.name>,
Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#67840] [PATCH 2/7] gnu: linux-libre 6.1: Update to 6.1.68.
Date: Fri, 15 Dec 2023 15:21:40 -0500 [thread overview]
Message-ID: <9c1f2d7b78b7ed0d6861480b1e33e2926259374f.1702671705.git.leo@famulari.name> (raw)
In-Reply-To: <85c4af655717eeabe775258db3ee379f8b0536a0.1702671705.git.leo@famulari.name>
* gnu/packages/linux.scm (linux-libre-6.1-version): Update to 6.1.68.
(linux-libre-6.1-pristine-source): Update hash.
Change-Id: I23cb34828bc0f31333ea737e566ee68967ed965e
---
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 86aa0f8dcd..3a88f79f53 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -511,7 +511,7 @@ (define-public linux-libre-6.6-pristine-source
;; The "longterm" kernels — the older releases with long-term upstream support.
;; Here are the support timelines:
;; <https://www.kernel.org/category/releases.html>
-(define-public linux-libre-6.1-version "6.1.67")
+(define-public linux-libre-6.1-version "6.1.68")
(define-public linux-libre-6.1-gnu-revision "gnu")
(define deblob-scripts-6.1
(linux-libre-deblob-scripts
@@ -521,7 +521,7 @@ (define deblob-scripts-6.1
(base32 "1hdibv43xbn1lv83i6qjgfmf1bvqxvq17fryfsq4r4sjgs9212js")))
(define-public linux-libre-6.1-pristine-source
(let ((version linux-libre-6.1-version)
- (hash (base32 "11cjqll3b7iq3mblwyzjrd5ph8avgk23f4mw4shm8j6ai5rdndvm")))
+ (hash (base32 "1qc4cwqlfni9i6mzh6arghdsd842hp9lb7s832dxw1p261mg4prn")))
(make-linux-libre-source version
(%upstream-linux-source version hash)
deblob-scripts-6.1)))
--
2.41.0
next prev parent reply other threads:[~2023-12-15 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 20:16 [bug#67840] Kernel updates Leo Famulari
2023-12-15 20:21 ` [bug#67840] [PATCH 1/7] gnu: linux-libre: Update to 6.6.7 Leo Famulari
2023-12-15 20:21 ` Leo Famulari [this message]
2023-12-15 20:21 ` [bug#67840] [PATCH 3/7] gnu: linux-libre 5.15: Update to 5.15.143 Leo Famulari
2023-12-15 20:21 ` [bug#67840] [PATCH 4/7] gnu: linux-libre 5.10: Update to 5.10.204 Leo Famulari
2023-12-15 20:21 ` [bug#67840] [PATCH 5/7] gnu: linux-libre 5.4: Update to 5.4.264 Leo Famulari
2023-12-15 20:21 ` [bug#67840] [PATCH 6/7] gnu: linux-libre 4.19: Update to 4.19.302 Leo Famulari
2023-12-15 20:21 ` [bug#67840] [PATCH 7/7] gnu: linux-libre 4.14: Update to 4.14.333 Leo Famulari
2023-12-16 21:01 ` bug#67840: [PATCH 1/7] gnu: linux-libre: Update to 6.6.7 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=9c1f2d7b78b7ed0d6861480b1e33e2926259374f.1702671705.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=67840@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=w@wmeyer.eu \
/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).