From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: 70723@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#70723] [PATCH 0/7] linux-libre kernel updates (2024-05-02)
Date: Sat, 4 May 2024 00:43:04 -0400 [thread overview]
Message-ID: <ZjW82FyVKPwEL6Ak@jasmine.lan> (raw)
In-Reply-To: <cover.1714677971.git.w@wmeyer.eu>
On Thu, May 02, 2024 at 09:28:34PM +0200, Wilko Meyer wrote:
> Hi Leo,
>
> there has been another round of updates again affecting all currently
> supported kernels. deblob scripts weren't uploaded yet, so I have yet to check
> if there are any changes to them.
>
> Wilko Meyer (7):
> gnu: linux-libre-6.8-gnu-revision: Update to 6.8.9.
> gnu: linux-libre 6.6: Update to 6.6.30.
> gnu: linux-libre 6.1: Update to 6.1.90.
> gnu: linux-libre 5.15: Update to 5.15.158.
> gnu: linux-libre 5.10: Update to 5.10.216.
> gnu: linux-libre 5.4: Update to 5.4.275.
> gnu: linux-libre 4.19: Update to 4.19.313.
Thanks! Pushed to 'kernel-updates'
next prev parent reply other threads:[~2024-05-04 4:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 19:28 [bug#70723] [PATCH 0/7] linux-libre kernel updates (2024-05-02) Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 1/7] gnu: linux-libre-6.8-gnu-revision: Update to 6.8.9 Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.30 Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.90 Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.158 Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.216 Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.275 Wilko Meyer
2024-05-02 19:31 ` [bug#70723] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.313 Wilko Meyer
2024-05-04 4:43 ` Leo Famulari [this message]
2024-05-06 3:24 ` bug#70723: [PATCH 0/7] linux-libre kernel updates (2024-05-02) 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=ZjW82FyVKPwEL6Ak@jasmine.lan \
--to=leo@famulari.name \
--cc=70723@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=w@wmeyer.eu \
/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.