From: Wilko Meyer <w@wmeyer.eu>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Need people to help with kernel updates
Date: Sat, 07 Oct 2023 20:31:58 +0200 [thread overview]
Message-ID: <87y1gdb1ws.fsf@wmeyer.eu> (raw)
In-Reply-To: <ZSGdrpP_VJinXVmt@jasmine.lan>
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> For a few years, I've been handling updates of the linux-libre kernel by
> myself.
First of all: thanks for doing this!
> The work itself is fairly mechanical and updates occur about once a
> week. It takes about 30 minutes to prepare the patches and push them to
> CI or send them to the mailing list.
I could imagine myself helping with these tasks. Practically this means,
that, whenever a new linux-libre minor update is being released, the
versions in linux-libre-* packages in gnu/packages/linux.scm have to be
bumped/a patch has to be sent?
Also: Is there anything to know/to have in mind when generating a new
kernel config for major releases?
> There is plenty of support for the CI and QA infrastructure to build the
> kernels, so you don't need a powerful computer.
How's the coverage for different ISA? Do the current CI jobs also cover
all the architectures we seem to support:
'("x86_64-linux" "i686-linux" "armhf-linux"
"aarch64-linux" "powerpc64le-linux" "riscv64-linux")
or are there cases where it could be beneficial to build locally first
using:
guix build -s $ISA linux-libre
for certain ISAs? I could use my workstation for this, if there's a
benefit to it.
> If you want to join in, please reply!
How would the communication around this be organized? If n>=2 people are
trying to work on the same set of tasks duplication may happen.
--
Kind regards,
Wilko Meyer
w@wmeyer.eu
next prev parent reply other threads:[~2023-10-08 14:54 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 [this message]
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
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=87y1gdb1ws.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).