From: Wilko Meyer <w@wmeyer.eu>
To: 68736@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>, leo@famulari.name
Subject: [bug#68736] [PATCH 0/7] linux-libre kernel updates (2024-01-25)
Date: Fri, 26 Jan 2024 16:09:57 +0100 [thread overview]
Message-ID: <20240126151000.11184-1-w@wmeyer.eu> (raw)
Hi Leo,
There has been another round of kernel updates. The FSFLA mirror isn't
updated yet, so I'll check back on wether the deblob scripts have
changed later.
Wilko Meyer (7):
gnu: linux-libre 6.7: Update to 6.7.2.
gnu: linux-libre 6.6: Update to 6.6.14.
gnu: linux-libre 6.1: Update to 6.1.75.
gnu: linux-libre 5.15: Update to 5.15.148.
gnu: linux-libre 5.10: Update to 5.10.209.
gnu: linux-libre 5.4: Update to 5.4.268.
gnu: linux-libre 4.19: Update to 4.19.306.
gnu/packages/linux.scm | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
--
2.41.0
next reply other threads:[~2024-01-26 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 15:09 Wilko Meyer [this message]
2024-01-26 15:37 ` [bug#68736] [PATCH 1/7] gnu: linux-libre 6.7: Update to 6.7.2 Wilko Meyer
2024-01-26 15:37 ` [bug#68736] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.14 Wilko Meyer
2024-01-26 15:37 ` [bug#68736] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.75 Wilko Meyer
2024-01-26 15:37 ` [bug#68736] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.148 Wilko Meyer
2024-01-26 15:37 ` [bug#68736] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.209 Wilko Meyer
2024-01-26 15:37 ` [bug#68736] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.268 Wilko Meyer
2024-01-26 15:37 ` [bug#68736] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.306 Wilko Meyer
2024-01-27 5:25 ` [bug#68736] [PATCH 1/7] gnu: linux-libre 6.7: Update to 6.7.2 Leo Famulari
2024-01-28 1:18 ` bug#68736: " Leo Famulari
2024-01-26 15:39 ` [bug#68736] linux-libre kernel updates (2024-01-25) Wilko Meyer
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=20240126151000.11184-1-w@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=68736@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 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.