From: Leo Famulari <leo@famulari.name>
To: 74449-done@debbugs.gnu.org
Subject: bug#74449: 2024-11-17 kernel updates
Date: Sun, 24 Nov 2024 18:36:34 -0500 [thread overview]
Message-ID: <Z0O4ggxX5WoXLGgc@jasmine.lan> (raw)
In-Reply-To: <Z0NqqmK1PC8-WERu@jasmine.lan>
On Sun, Nov 24, 2024 at 01:04:26PM -0500, Leo Famulari wrote:
> I pushed the first 6 patches of this series as
> c05a78739de9ad2ca2ea97c5899d9b73fca620ea
>
> I've had to amend the commit of the 4.19 kernel series to 4.19.324
> because it had the wrong commit hashes. It's building on the
> 'kernel-updates' branch.
>
> The problem was that I fetched release artifacts for 4.19.234, not
> 4.19.324. Oops!
>
> Updated patch attached
Pushed as 0de78424bd27ec97633401c735e0a766a79b2eee
prev parent reply other threads:[~2024-11-24 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 0:30 [bug#74449] 2024-11-17 kernel updates Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 1/7] gnu: linux-libre: Update to 6.11.9 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.62 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.118 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.173 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.230 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.286 Leo Famulari
2024-11-21 0:39 ` [bug#74449] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.324 Leo Famulari
2024-11-24 18:04 ` [bug#74449] 2024-11-17 kernel updates Leo Famulari
2024-11-24 23:36 ` Leo Famulari [this message]
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=Z0O4ggxX5WoXLGgc@jasmine.lan \
--to=leo@famulari.name \
--cc=74449-done@debbugs.gnu.org \
/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.