From: Greg KH <gregkh@linuxfoundation.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Sasha Levin <sashal@kernel.org>, WANG Xuerui <kernel@xen0n.name>,
Bibo Mao <maobibo@loongson.cn>,
loongarch@lists.linux.dev, stable@vger.kernel.org
Subject: Re: stable-rc/linux-6.10.y: error: no member named 'st' in 'struct kvm_vcpu_arch'
Date: Mon, 30 Sep 2024 20:33:52 +0200 [thread overview]
Message-ID: <2024093040-onslaught-camping-3faf@gregkh> (raw)
In-Reply-To: <CAAhV-H4WLByJ53oqQgEnVjy4bT0pS77fT5BA4NaCp8AOn+cyJw@mail.gmail.com>
On Sun, Sep 29, 2024 at 09:02:33AM +0800, Huacai Chen wrote:
> On Sat, Sep 28, 2024 at 8:29 PM Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
> >
> > Hi Sasha, LoongArch,
> >
> > In a stable-rc/linux-6.10.y build-test today, I got:
> >
> > arch/loongarch/kvm/vcpu.c:575:15: error: no member named 'st' in
> > 'struct kvm_vcpu_arch'
> > 575 | vcpu->arch.st.guest_addr = 0;
> >
> > which I guess is triggered by missing prerequisites for commit
> > 56f7eeae40de ("LoongArch: KVM: Invalidate guest steal time address on
> > vCPU reset").
> Hmm, please drop the backported patch "LoongArch: KVM: Invalidate
> guest steal time address on vCPU reset".
Ick, missed this, can you please send a revert?
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-30 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 12:29 stable-rc/linux-6.10.y: error: no member named 'st' in 'struct kvm_vcpu_arch' Miguel Ojeda
2024-09-29 1:02 ` Huacai Chen
2024-09-30 18:33 ` Greg KH [this message]
2024-10-01 7:25 ` [PATCH 6.10.y] Revert "LoongArch: KVM: Invalidate guest steal time address on vCPU reset" Huacai Chen
2024-10-01 7:56 ` Greg KH
2024-10-01 8:55 ` Huacai Chen
2024-10-01 10:12 ` Greg KH
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=2024093040-onslaught-camping-3faf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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