From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: 66751@debbugs.gnu.org
Subject: [bug#66751] [PATCH 0/7] linux-libre kernel updates (2023-10-25)
Date: Fri, 27 Oct 2023 00:15:02 -0400 [thread overview]
Message-ID: <ZTs5RuPnsMMiZFsa@jasmine.lan> (raw)
In-Reply-To: <20231025221136.12525-1-w@wmeyer.eu>
On Thu, Oct 26, 2023 at 12:11:26AM +0200, Wilko Meyer wrote:
> Hi Leo,
>
> We had seven kernel releases yesterday, so I bumped each package to the
> latest minor version.
Thanks! I saw it failed to apply on qa.guix.gnu.org, so I applied the
patches locally, rebased on current master branch, and sent a v2 patch
series, as well as pushing to a 'kernel-updates' branch.
https://qa.guix.gnu.org/issue/66751
next prev parent reply other threads:[~2023-10-27 4:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 22:11 [bug#66751] [PATCH 0/7] linux-libre kernel updates (2023-10-25) Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 1/7] gnu: linux-libre 6.5: Update to 6.5.9 Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 2/7] gnu: linux-libre 6.1: Update to 6.1.60 Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 3/7] gnu: linux-libre 5.15: Update to 5.15.137 Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 4/7] gnu: linux-libre 5.10: Update to 5.10.199 Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 5/7] gnu: linux-libre 5.4: Update to 5.4.259 Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 6/7] gnu: linux-libre 4.19: Update to 4.19.297 Wilko Meyer
2023-10-25 22:14 ` [bug#66751] [PATCH 7/7] gnu: linux-libre 4.14: Update to 4.14.328 Wilko Meyer
2023-10-26 15:06 ` [bug#66751] [PATCH 0/7] linux-libre kernel updates (2023-10-25) Wilko Meyer
2023-10-27 4:15 ` Leo Famulari [this message]
2023-10-27 4:15 ` [bug#66751] [PATCH v2 1/7] gnu: linux-libre 6.5: Update to 6.5.9 Leo Famulari
2023-10-27 4:15 ` [bug#66751] [PATCH v2 2/7] gnu: linux-libre 6.1: Update to 6.1.60 Leo Famulari
2023-10-27 4:15 ` [bug#66751] [PATCH v2 3/7] gnu: linux-libre 5.15: Update to 5.15.137 Leo Famulari
2023-10-27 4:15 ` [bug#66751] [PATCH v2 4/7] gnu: linux-libre 5.10: Update to 5.10.199 Leo Famulari
2023-10-27 4:15 ` [bug#66751] [PATCH v2 5/7] gnu: linux-libre 5.4: Update to 5.4.259 Leo Famulari
2023-10-27 4:15 ` [bug#66751] [PATCH v2 6/7] gnu: linux-libre 4.19: Update to 4.19.297 Leo Famulari
2023-10-27 4:15 ` [bug#66751] [PATCH v2 7/7] gnu: linux-libre 4.14: Update to 4.14.328 Leo Famulari
2023-10-28 5:21 ` bug#66751: [PATCH v2 1/7] gnu: linux-libre 6.5: Update to 6.5.9 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=ZTs5RuPnsMMiZFsa@jasmine.lan \
--to=leo@famulari.name \
--cc=66751@debbugs.gnu.org \
--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.