From: Sean Christopherson <seanjc@google.com>
To: Like Xu <like.xu.linux@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH] KVM: x86/xsave: Remove 'return void' expression for 'void function'
Date: Wed, 25 Oct 2023 18:10:12 -0700 [thread overview]
Message-ID: <ZTm8dH1GQ3vQtQua@google.com> (raw)
In-Reply-To: <ZTklnN2I3gYjGxVv@google.com>
On Wed, Oct 25, 2023, Sean Christopherson wrote:
> On Wed, Oct 25, 2023, Like Xu wrote:
> > Emm, did we miss this little fix ?
>
> No, I have it earmarked, it's just not a priority because it doesn't truly fix
> anything. Though I suppose it probably makes to apply it for 6.8, waiting one
> more day to send PULL requests to Paolo isn't a problem.
Heh, when I tried to apply this I got reminded of why I held it for later. I
want to apply it to kvm-x86/misc, but that's based on ~6.6-rc2 (plus a few KVM
patches), i.e. doesn't have the "buggy" commit. I don't want to rebase "misc",
nor do I want to create a branch and PULL request for a single trivial commit.
So for logistical reasons, I'm not going apply this right away, but I will make
sure it gets into v6.7.
next prev parent reply other threads:[~2023-10-26 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 6:40 [PATCH] KVM: x86/xsave: Remove 'return void' expression for 'void function' Like Xu
2023-10-10 16:12 ` Maxim Levitsky
2023-10-25 11:24 ` Like Xu
2023-10-25 14:26 ` Sean Christopherson
2023-10-26 1:10 ` Sean Christopherson [this message]
2023-11-30 6:10 ` Like Xu
2023-11-30 16:25 ` Sean Christopherson
2023-12-01 23:30 ` Sean Christopherson
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=ZTm8dH1GQ3vQtQua@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.