From: Wilko Meyer <w@wmeyer.eu>
To: 70388@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>,
leo@famulari.name, Leo Famulari <leo@famulari.name>,
Tobias Geerinckx-Rice <me@tobias.gr>, Wilko Meyer <w@wmeyer.eu>
Subject: [bug#70388] [PATCH 0/7] linux-libre kernel updates (2024-04-14)
Date: Sun, 14 Apr 2024 22:01:50 +0200 [thread overview]
Message-ID: <cover.1713124818.git.w@wmeyer.eu> (raw)
Hi Leo,
There has been another round of updates again, this time with changed deblob
scripts in the 6.x series kernels.
Wilko Meyer (7):
gnu: linux-libre 6.8: Update to 6.8.6.
gnu: linux-libre 6.6: Update to 6.6.27.
gnu: linux-libre 6.1: Update to 6.1.86.
gnu: linux-libre 5.15: Update to 5.15.155.
gnu: linux-libre 5.10: Update to 5.10.215.
gnu: linux-libre 5.4: Update to 5.4.274.
gnu: linux-libre 4.19: Update to 4.19.312.
gnu/packages/linux.scm | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
base-commit: 803f092ab6fd98642ded4ec4486658a230879967
--
2.41.0
next reply other threads:[~2024-04-14 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 20:01 Wilko Meyer [this message]
2024-04-14 20:05 ` [bug#70388] [PATCH 1/7] gnu: linux-libre 6.8: Update to 6.8.6 Wilko Meyer
2024-04-14 20:05 ` [bug#70388] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.27 Wilko Meyer
2024-04-14 20:05 ` [bug#70388] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.86 Wilko Meyer
2024-04-14 20:05 ` [bug#70388] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.155 Wilko Meyer
2024-04-14 20:05 ` [bug#70388] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.215 Wilko Meyer
2024-04-14 20:05 ` [bug#70388] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.274 Wilko Meyer
2024-04-14 20:05 ` [bug#70388] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.312 Wilko Meyer
2024-04-15 4:02 ` [bug#70388] [PATCH 0/7] linux-libre kernel updates (2024-04-14) Leo Famulari
2024-04-16 15:25 ` bug#70388: " 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.1713124818.git.w@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=70388@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).