unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Wilko Meyer <w@wmeyer.eu>
To: 67513@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>, leo@famulari.name
Subject: [bug#67513] [PATCH 3/8] gnu: linux-libre 6.1: Update to 6.1.64.
Date: Tue, 28 Nov 2023 21:39:44 +0100	[thread overview]
Message-ID: <20231128203951.9143-3-w@wmeyer.eu> (raw)
In-Reply-To: <20231128203951.9143-1-w@wmeyer.eu>

* gnu/packages/linux.scm (linux-libre-6.1-version): Update to 6.1.64.
(linux-libre-6.1-pristine-source): Update hash.
---
 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 014f3617d2..0bfd0cdd01 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -526,7 +526,7 @@ (define-public linux-libre-6.5-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.63")
+(define-public linux-libre-6.1-version "6.1.64")
 (define-public linux-libre-6.1-gnu-revision "gnu")
 (define deblob-scripts-6.1
   (linux-libre-deblob-scripts
@@ -536,7 +536,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 "13bmy22mi4ybl21kr3hdy6qiaawiqz2jgl2gl9hwqkyx04xh97f2")))
+        (hash (base32 "1ry7dp39010hfja1wial6r6q6ilgygwm7gdz22bg4rzaycwam7b2")))
    (make-linux-libre-source version
                             (%upstream-linux-source version hash)
                             deblob-scripts-6.1)))
-- 
2.41.0





  parent reply	other threads:[~2023-11-28 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 20:34 [bug#67513] [PATCH 0/8] WIP: linux-libre kernel updates (2023-11-28) Wilko Meyer
2023-11-28 20:39 ` [bug#67513] [PATCH 1/8] gnu: linux-libre 6.6: Update to 6.6.3 Wilko Meyer
2023-11-28 20:39   ` [bug#67513] [PATCH 2/8] gnu: linux-libre 6.5: Update to 6.5.13 Wilko Meyer
2023-11-28 20:39   ` Wilko Meyer [this message]
2023-11-28 20:39   ` [bug#67513] [PATCH 4/8] gnu: linux-libre 5.15: Update to 5.15.140 Wilko Meyer
2023-11-28 20:39   ` [bug#67513] [PATCH 5/8] gnu: linux-libre 5.10: Update to 5.10.202 Wilko Meyer
2023-11-28 20:39   ` [bug#67513] [PATCH 6/8] gnu: linux-libre 5.4: Update to 5.4.262 Wilko Meyer
2023-11-28 20:39   ` [bug#67513] [PATCH 7/8] gnu: linux-libre 4.19: Update to 4.19.300 Wilko Meyer
2023-11-28 20:39   ` [bug#67513] [PATCH 8/8] gnu: linux-libre 4.14: Update to 4.14.331 Wilko Meyer
2023-11-29 13:37 ` [bug#67513] [PATCH 0/8] WIP: linux-libre kernel updates (2023-11-28) Wilko Meyer
2023-11-29 18:08 ` Leo Famulari
2023-12-05  2:37   ` bug#67513: " 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=20231128203951.9143-3-w@wmeyer.eu \
    --to=w@wmeyer.eu \
    --cc=67513@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).