[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200526152152.GA1194141@xz-x1>
Date: Tue, 26 May 2020 11:21:52 -0400
From: Peter Xu <peterx@...hat.com>
To: kbuild test robot <lkp@...el.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
kbuild-all@...ts.01.org, Vitaly Kuznetsov <vkuznets@...hat.com>,
Alex Williamson <alex.williamson@...hat.com>,
"Michael S . Tsirkin" <mst@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"Dr . David Alan Gilbert" <dgilbert@...hat.com>,
Christophe de Dinechin <dinechin@...hat.com>,
Jason Wang <jasowang@...hat.com>,
Kevin Tian <kevin.tian@...el.com>
Subject: Re: [PATCH v9 07/14] KVM: Don't allocate dirty bitmap if dirty ring
is enabled
On Tue, May 26, 2020 at 11:05:47PM +0800, kbuild test robot wrote:
> >> arch/x86/kvm/mmu/mmu.c:1280:3: warning: Returning an integer in a function with pointer return type is not portable. [CastIntegerToAddressAtReturn]
> return false;
> ^
A rebase accident for quite a few versions... Fixed.
--
Peter Xu
Powered by blists - more mailing lists