Dave Voutila writes:
> Just a heads up, if you use vmm_clock[1] and virtio_vmmci[2] kernel
> modules that I maintain, you'll need to pull the latest.
>
> Folks in Linux Land decided to twiddle some of the API surface area
> forcing me to add yet another block of #elif's and kernel version checks
izzy Meyer writes:
> On Thu, 05 Dec 2024 14:13:03 -0500
> Dave Voutila wrote:
>
>> Just a heads up, if you use vmm_clock[1] and virtio_vmmci[2] kernel
>> modules that I maintain, you'll need to pull the latest.
>>
>
>
> Great work! I just tried this out on my laptop with a Devuan 5 VM and a
>
On Thu, 05 Dec 2024 14:13:03 -0500
Dave Voutila wrote:
> Just a heads up, if you use vmm_clock[1] and virtio_vmmci[2] kernel
> modules that I maintain, you'll need to pull the latest.
>
> Folks in Linux Land decided to twiddle some of the API surface area
> forcing me to add yet another block of
Just a heads up, if you use vmm_clock[1] and virtio_vmmci[2] kernel
modules that I maintain, you'll need to pull the latest.
Folks in Linux Land decided to twiddle some of the API surface area
forcing me to add yet another block of #elif's and kernel version checks
to the vmmci(4) implementation.
4 matches
Mail list logo