From: Wilko Meyer <w@wmeyer.eu>
To: 71611@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>, Leo Famulari <leo@famulari.name>,
Tobias Geerinckx-Rice <me@tobias.gr>, Wilko Meyer <w@wmeyer.eu>
Subject: [bug#71611] [PATCH 0/7] linux-libre kernel updates (2024-06-17)
Date: Mon, 17 Jun 2024 14:20:39 +0200 [thread overview]
Message-ID: <cover.1718626732.git.w@wmeyer.eu> (raw)
Hi Leo,
There's been a round of kernel updates for all currently supported
kernels. Deblob scripts didn't change.
Wilko Meyer (7):
gnu: linux-libre 6.9: Update to 6.9.5.
gnu: linux-libre 6.6: Update to 6.6.34.
gnu: linux-libre 6.1: Update to 6.1.94.
gnu: linux-libre 5.15: Update to 5.15.161.
gnu: linux-libre 5.10: Update to 5.10.219.
gnu: linux-libre 5.4: Update to 5.4.278.
gnu: linux-libre 4.19: Update to 4.19.316.
gnu/packages/linux.scm | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
base-commit: 5d5dc71e25011d215755666568a88940e80d8e7d
--
2.41.0
next reply other threads:[~2024-06-17 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 12:20 Wilko Meyer [this message]
2024-06-17 12:26 ` [bug#71611] [PATCH 1/7] gnu: linux-libre 6.9: Update to 6.9.5 Wilko Meyer
2024-06-17 12:26 ` [bug#71611] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.34 Wilko Meyer
2024-06-17 12:26 ` [bug#71611] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.94 Wilko Meyer
2024-06-17 12:26 ` [bug#71611] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.161 Wilko Meyer
2024-06-17 12:26 ` [bug#71611] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.219 Wilko Meyer
2024-06-17 12:26 ` [bug#71611] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.278 Wilko Meyer
2024-06-17 12:26 ` [bug#71611] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.316 Wilko Meyer
2024-06-17 16:09 ` [bug#71611] [PATCH 0/7] linux-libre kernel updates (2024-06-17) Leo Famulari
2024-06-19 17:26 ` bug#71611: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1718626732.git.w@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=71611@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.