From: Wilko Meyer <w@wmeyer.eu>
To: Leo Famulari <leo@famulari.name>
Cc: Wilko Meyer <w@wmeyer.eu>, guix-devel@gnu.org
Subject: Re: Need people to help with kernel updates
Date: Sun, 29 Oct 2023 13:15:01 +0100 [thread overview]
Message-ID: <87il6pr4x6.fsf@wmeyer.eu> (raw)
In-Reply-To: <ZT1sZ7dYT-3cQddB@jasmine.lan>
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> It seems that linux-libre 6.6 will be released soon.
Yes, probably within the next(?) week if I read this mail[0] on lkml
right as there'll probably be a rc8. There already seem to be a 6.6
branch in the linux-libre project introducing the deblob scripts:
commit 8437b2928c7fd032657f571974c004130f940956 (HEAD -> scripts/6.6,
tag: scripts/v6.6-rc7-gnu, origin/scripts/6.6)
> Would anyone like to try their hand at packaging it for Guix? Wilko, do
> you feel up to it?
Sure thing! I'll start packaging it as soon as 6.6 is released and the
deblob scripts for that release are ready.
> As I mentioned previously, this requires a bit more work than minor
> kernel upgrades because the kernel configs need to be updated.
>
> I'm happy to assist with this, give advice, etc.
Thank you for this, I'll reach out if I experience any blockers or need
help during the process of packaging the 6.6 release.
[0]: https://lore.kernel.org/all/CAHk-=whqsbGgnoeYeEuP9fabaZrpPDA=SySMBe3TfQQqVMHvBA@mail.gmail.com/
--
Kind regards,
Wilko Meyer
w@wmeyer.eu
next prev parent reply other threads:[~2023-10-29 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 18:04 Need people to help with kernel updates Leo Famulari
2023-10-07 18:31 ` Wilko Meyer
2023-10-08 18:12 ` Leo Famulari
2023-10-09 16:21 ` Wilko Meyer
2023-10-10 11:18 ` Leo Famulari
2023-10-10 14:13 ` wolf
2023-10-12 12:15 ` Wilko Meyer
2023-10-12 18:44 ` Leo Famulari
2023-10-15 19:58 ` Wilko Meyer
2023-10-28 20:17 ` Leo Famulari
2023-10-29 12:15 ` Wilko Meyer [this message]
2023-10-09 1:22 ` John Kehayias
2023-10-09 13:22 ` Luis Felipe
2023-10-14 15:48 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il6pr4x6.fsf@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).