qemu-devel
[Top][All Lists]
Advanced

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

Re: [PATCH 3/4] linux-headers: Update to current kvm/next


From: Cornelia Huck
Subject: Re: [PATCH 3/4] linux-headers: Update to current kvm/next
Date: Mon, 03 Jun 2024 17:58:55 +0200
User-agent: Notmuch/0.38.3 (https://notmuchmail.org)

On Mon, Jun 03 2024, Paolo Bonzini <[email protected]> wrote:

> From: Pankaj Gupta <[email protected]>
>
> Also brings in an linux-headers/linux/vhost.h fix from v6.9-rc4.
>
> Co-developed-by: Michael Roth <[email protected]>
> Signed-off-by: Michael Roth <[email protected]>
> Signed-off-by: Pankaj Gupta <[email protected]>
> Message-ID: <[email protected]>
> Signed-off-by: Paolo Bonzini <[email protected]>
> ---
>  linux-headers/asm-loongarch/kvm.h |  4 +++
>  linux-headers/asm-riscv/kvm.h     |  1 +
>  linux-headers/asm-x86/kvm.h       | 52 ++++++++++++++++++++++++++++++-
>  linux-headers/linux/vhost.h       | 15 ++++-----
>  4 files changed, 64 insertions(+), 8 deletions(-)

Hm, I'm not sure updating to kvm/next is a good idea ("current kvm/next"
does not mean anything without a commit hash anyway.) I think we should
only update to something that's in Linus' tree already... how stable is
kvm/next?




reply via email to

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