[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <073cdc28-6dbb-a2d1-ee1b-f3b53d5b7c81@redhat.com>
Date: Tue, 18 Jan 2022 12:44:10 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Christian Borntraeger <borntraeger@...ux.ibm.com>,
dwmw2@...radead.org
Cc: butterflyhuangxx@...il.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, seanjc@...gle.com,
Cornelia Huck <cohuck@...hat.com>,
Janosch Frank <frankja@...ux.ibm.com>,
David Hildenbrand <david@...hat.com>,
linux-s390 <linux-s390@...r.kernel.org>,
Thomas Huth <thuth@...hat.com>,
Claudio Imbrenda <imbrenda@...ux.ibm.com>
Subject: Re: [PATCH] KVM: avoid warning on s390 in mark_page_dirty
On 1/18/22 09:53, Christian Borntraeger wrote:
>>>
>>> Paolo, are you going to pick this for next for the time being?
>>>
>>
>> Yep, done now.
>>
>> Paolo
>
> Thanks. I just realized that Davids patch meanwhile landed in Linus
> tree. So better
> take this via master and not next.
Yeah, I understood what you meant. :) In fact, "master" right now is
still on 5.16 (for patches that are destined to stable, but have
conflicts merge window changes; those are pushed to master and merged
from there into next). There will be another pull request this week and
it will have this patch.
> Maybe also add
> Fixes: 2efd61a608b0 ("KVM: Warn if mark_page_dirty() is called without
> an active vCPU")
> in case the patch is picked for stable
Ok, will do.
Paolo
Powered by blists - more mailing lists