From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: applied: [PATCH pve-kernel 0/3] enable CONFIG_RUST and fix sbuild target with extra-package revision
Date: Tue, 31 Mar 2026 23:44:26 +0200 [thread overview]
Message-ID: <177499345762.839800.14198093445424733664.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260227152207.3079037-1-s.ivanov@proxmox.com>
On Fri, 27 Feb 2026 16:21:35 +0100, Stoiko Ivanov wrote:
> This patchset is the result of testing the effect of enabling CONFIG_RUST
> in our current kernel configuration.
>
> * enabling this entails changes to the needed firmware and the kernel ABI
> (I still skipped the updated fwlist and abi-prev files, as the diffs are
> huge and best generated when actually building a kernel with this
> enabled
> * built was done locally and once with `make sbuild` (PATCH 1/3 fixed
> `make sbuild` with PKG_REV_EXTRA=~testrust1 for me).
> * tested the resulting kernel on 2 VMs with ZFS as /, and on a physical
> test-server in our lab (with PVE 8.4 installed at that time).
> both tests looked ok.
>
> [...]
Applied, thanks!
[1/3] d/control: add dependencies for CONFIG_RUST
commit: 31bafb7f8472b565a322b9c629a76e93fbf99e65
[2/3] d/rules: explicitly enable CONFIG_RUST
commit: 6fd5503d87a8081aa36c466b1756d8b29125b614
[3/3] make: fix DSC variable name
commit: 4732d62f7042206149c24a1249fbd4ef36f8df21
prev parent reply other threads:[~2026-03-31 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:21 Stoiko Ivanov
2026-02-27 15:21 ` [PATCH pve-kernel 1/3] d/control: add dependencies for CONFIG_RUST Stoiko Ivanov
2026-02-27 15:21 ` [PATCH pve-kernel 2/3] d/rules: explicitly enable CONFIG_RUST Stoiko Ivanov
2026-02-27 15:21 ` [PATCH pve-kernel 3/3] make: fix DSC variable name Stoiko Ivanov
2026-03-31 21:44 ` Thomas Lamprecht [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=177499345762.839800.14198093445424733664.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox