From: Cornelia Huck <cohuck@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: thuth@redhat.com, Pankaj Gupta <pankaj.gupta@amd.com>,
Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH 3/4] linux-headers: Update to current kvm/next
Date: Mon, 03 Jun 2024 17:58:55 +0200 [thread overview]
Message-ID: <874jaam30g.fsf@redhat.com> (raw)
In-Reply-To: <20240603131141.834241-4-pbonzini@redhat.com>
On Mon, Jun 03 2024, Paolo Bonzini <pbonzini@redhat.com> wrote:
> From: Pankaj Gupta <pankaj.gupta@amd.com>
>
> Also brings in an linux-headers/linux/vhost.h fix from v6.9-rc4.
>
> Co-developed-by: Michael Roth <michael.roth@amd.com>
> Signed-off-by: Michael Roth <michael.roth@amd.com>
> Signed-off-by: Pankaj Gupta <pankaj.gupta@amd.com>
> Message-ID: <20240530111643.1091816-3-pankaj.gupta@amd.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> 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?
next prev parent reply other threads:[~2024-06-03 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 13:11 [PATCH 0/4] update-linux-headers: prepare for updating to 6.9+ and for SNP patches Paolo Bonzini
2024-06-03 13:11 ` [PATCH 1/4] update-linux-headers: fix forwarding to asm-generic headers Paolo Bonzini
2024-06-03 14:54 ` Thomas Huth
2024-06-03 13:11 ` [PATCH 2/4] update-linux-headers: move pvpanic.h to correct directory Paolo Bonzini
2024-06-03 14:58 ` Thomas Huth
2024-06-03 13:11 ` [PATCH 3/4] linux-headers: Update to current kvm/next Paolo Bonzini
2024-06-03 15:58 ` Cornelia Huck [this message]
2024-06-03 16:01 ` Paolo Bonzini
2024-06-03 16:25 ` Cornelia Huck
2024-06-03 16:40 ` Paolo Bonzini
2024-06-03 13:11 ` [PATCH 4/4] update-linux-headers: import linux/kvm_para.h header Paolo Bonzini
2024-06-03 15:05 ` Thomas Huth
2024-06-04 8:31 ` [PATCH 0/4] update-linux-headers: prepare for updating to 6.9+ and for SNP patches Cornelia Huck
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=874jaam30g.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=michael.roth@amd.com \
--cc=pankaj.gupta@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).