From: Wilko Meyer <w@wmeyer.eu>
To: 67951@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>, leo@famulari.name
Subject: [bug#67951] [PATCH 0/7] linux-libre kernel-updates (2023-12-20)
Date: Thu, 21 Dec 2023 14:31:20 +0100 [thread overview]
Message-ID: <cover.1703165335.git.w@wmeyer.eu> (raw)
Hi Leo,
there have been recent kernel-updates again; as far as I can tell the
hashes of the deblob scripts didn't change, so we just had to adjust the
linux tarball hashes.
Kind regards,
Wilko Meyer
Wilko Meyer (7):
gnu: linux-libre 6.6: Update to 6.6.8.
gnu: linux-libre 6.1: Update to 6.1.69.
gnu: linux-libre 5.15: Update to 5.15.144.
gnu: linux-libre 5.10: Update to 5.10.205.
gnu: linux-libre 5.4: Update to 5.4.265.
gnu: linux-libre 4.19: Update to 4.19.303.
gnu: linux-libre 4.14: Update to 4.14.334.
gnu/packages/linux.scm | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
base-commit: dca3fe2adc14c664ff45b35a7b15d81b40a742a6
--
2.41.0
next reply other threads:[~2023-12-21 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:31 Wilko Meyer [this message]
2023-12-21 13:32 ` [bug#67951] [PATCH 1/7] gnu: linux-libre 6.6: Update to 6.6.8 Wilko Meyer
2023-12-26 13:58 ` bug#67951: " Leo Famulari
2023-12-21 13:32 ` [bug#67951] [PATCH 2/7] gnu: linux-libre 6.1: Update to 6.1.69 Wilko Meyer
2023-12-21 13:32 ` [bug#67951] [PATCH 3/7] gnu: linux-libre 5.15: Update to 5.15.144 Wilko Meyer
2023-12-21 13:32 ` [bug#67951] [PATCH 4/7] gnu: linux-libre 5.10: Update to 5.10.205 Wilko Meyer
2023-12-21 13:32 ` [bug#67951] [PATCH 5/7] gnu: linux-libre 5.4: Update to 5.4.265 Wilko Meyer
2023-12-21 13:32 ` [bug#67951] [PATCH 6/7] gnu: linux-libre 4.19: Update to 4.19.303 Wilko Meyer
2023-12-21 13:32 ` [bug#67951] [PATCH 7/7] gnu: linux-libre 4.14: Update to 4.14.334 Wilko Meyer
2023-12-21 17:03 ` [bug#67951] [PATCH 0/7] linux-libre kernel-updates (2023-12-20) 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=cover.1703165335.git.w@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=67951@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).