guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need people to help with kernel updates


From: Wilko Meyer
Subject: Re: Need people to help with kernel updates
Date: Sun, 15 Oct 2023 21:58:26 +0200

Hi Leo,

Leo Famulari <leo@famulari.name> writes:
> I pushed your patches as 06acda9715711c406f30b3a314387002244d8792

Thank you for this!

> Overall, the fact that qa.guix.gnu.org is successfully building across
> so many architectures means that we have a strong foundation for the
> future of building kernel packages in Guix.

This sounds good; good to see how many builds were actually succesful
on guixes QA!

> Thanks you for taking the initiative to write the patches and manage QA
> for this latest round of updates!
>
> I'm curious, now that we've done a round, do you have any thoughts about
> the work so far?

Thanks to the scripts you've provided and the initial explaination
you've given it was fairly easy to pick up the work of bumping the minor
kernel versions so far. I already followed new kernel releases closely
before, so figuring out when actions are required (as in when new minor
versions were available) wasn't too much of an issue. With 6.6 around
the corner soonish, I wonder how making a new kernel config for that
major release will go/what there'll be to learn in that regards. Until
now the whole process seems to be quite easy to pick up, but does
require constant recurring attention around each new minor release.

There's been a 6.1.58 stable release a few hours ago[0], with changing
mostly affecting the NFS subsystem (changes being almost exclusively
reverts of commits). I created a patch[1] for this, if you'd have a
minute to spare (or anyone else with appropriate rights to apply it on
the kernel-updates branch; as I can't do it myself), we could see if it
builds/merge it to master later on if it looks good.

[0]: https://lore.kernel.org/lkml/2023101518-subscript-entity-be71@gregkh/
[1]: https://issues.guix.gnu.org/66568

-- 
Kind regards,

Wilko Meyer
w@wmeyer.eu



reply via email to

[Prev in Thread] Current Thread [Next in Thread]