From: Tomas Volf <wolf@wolfsden.cz>
To: 65061@debbugs.gnu.org
Cc: Tomas Volf <wolf@wolfsden.cz>, Leo Famulari <leo@famulari.name>,
Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#65061] [PATCH] gnu: linux-libre 6.1: Update to 6.1.43.
Date: Sat, 5 Aug 2023 02:14:48 +0200 [thread overview]
Message-ID: <a698da89023db4a503cffa21a3d1f49097e7f0d8.1691194488.git.wolf@wolfsden.cz> (raw)
* gnu/packages/linux.scm (deblob-scripts-6.1): Update hash.
(linux-libre-6.1-pristine-source): Update hash.
(linux-libre-6.1-source): Remove upstreamed patch.
(linux-libre-6.1-version): Update to 6.1.43.
---
gnu/packages/linux.scm | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 3aec03a3ec..c00e38a1d1 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -520,17 +520,17 @@ (define-public linux-libre-6.3-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.38")
+(define-public linux-libre-6.1-version "6.1.43")
(define-public linux-libre-6.1-gnu-revision "gnu")
(define deblob-scripts-6.1
(linux-libre-deblob-scripts
linux-libre-6.1-version
linux-libre-6.1-gnu-revision
- (base32 "1b96867b46m36l88qnq2d4i9y43ghw97z9jajrh11cvb6kq4xi67")
- (base32 "1qq3nsznblz5fkwahxwq26csmrmjbxh8xknm2z4zw6b6k9svzb1b")))
+ (base32 "1sf80f2i4vf888xjcn84ymn4w5ynn30ib9033zwmv7f09yvfhapy")
+ (base32 "1liv6s1f1k52nkljsak0i42wyvfsj2b0156rhdh3cmginb98xb37")))
(define-public linux-libre-6.1-pristine-source
(let ((version linux-libre-6.1-version)
- (hash (base32 "0hrdh1w9z8bgy4cxqsxfkwa01yincfw1mq1bbwm36zczc0dzk97r")))
+ (hash (base32 "02588pl1z8jxgxpa03rsdyg5pr0r3v0aylzp8r5ykm32193lhli4")))
(make-linux-libre-source version
(%upstream-linux-source version hash)
deblob-scripts-6.1)))
@@ -658,8 +658,7 @@ (define-public linux-libre-6.1-source
(list %boot-logo-patch
%linux-libre-arm-export-__sync_icache_dcache-patch)
(search-patches
- "linux-libre-infodocs-target.patch"
- "linux-libre-wireguard-postup-privkey.patch"))))
+ "linux-libre-infodocs-target.patch"))))
(define-public linux-libre-5.15-source
(source-with-patches linux-libre-5.15-pristine-source
base-commit: 17fadbb5ea3b35f962ab1bcd5b8cf4e1d699eb7e
--
2.41.0
next reply other threads:[~2023-08-05 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 0:14 Tomas Volf [this message]
[not found] ` <handler.65061.B.169119454121203.ack@debbugs.gnu.org>
2023-08-11 17:37 ` [bug#65061] obsolete wolf
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=a698da89023db4a503cffa21a3d1f49097e7f0d8.1691194488.git.wolf@wolfsden.cz \
--to=wolf@wolfsden.cz \
--cc=65061@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
/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).