From: Sean Christopherson <seanjc@google.com>
To: "Carlos López" <clopez@suse.de>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev, alex.williamson@redhat.com,
pbonzini@redhat.com, open list <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: VFIO: use mutex guard in kvm_vfio_file_set_spapr_tce()
Date: Fri, 17 Apr 2026 06:31:16 -0700 [thread overview]
Message-ID: <aeI2JCLldUFff0Q0@google.com> (raw)
In-Reply-To: <ce3e8a51-63fe-4723-b1d8-6555b8b77817@suse.de>
On Fri, Apr 17, 2026, Carlos López wrote:
> On 4/7/26 5:48 AM, kernel test robot wrote:
> > Hi Carlos,
> >
> > kernel test robot noticed the following build warnings:
> >
> > [auto build test WARNING on d2ea4ff1ce50787a98a3900b3fb1636f3620b7cf]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Carlos-L-pez/KVM-VFIO-clean-up-control-flow-in-kvm_vfio_file_add/20260314-053050
> > base: d2ea4ff1ce50787a98a3900b3fb1636f3620b7cf
> > patch link: https://lore.kernel.org/r/20260313122040.1413091-5-clopez%40suse.de
> > patch subject: [PATCH 2/4] KVM: VFIO: use mutex guard in kvm_vfio_file_set_spapr_tce()
> > config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20260403/202604031640.vckbuS2S-lkp@intel.com/config)
> > compiler: powerpc64-linux-gcc (GCC) 15.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260403/202604031640.vckbuS2S-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202604031640.vckbuS2S-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > arch/powerpc/kvm/../../../virt/kvm/vfio.c: In function 'kvm_vfio_file_set_spapr_tce':
> >>> arch/powerpc/kvm/../../../virt/kvm/vfio.c:219:13: warning: unused variable 'ret' [-Wunused-variable]
> > 219 | int ret;
> > | ^~~
> >
>
> Sean, should I send a v2 for this or will you fix it up when applying?
I'll fixup when applying.
next prev parent reply other threads:[~2026-04-17 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260313122040.1413091-3-clopez@suse.de>
2026-03-13 12:20 ` [PATCH 1/4] KVM: VFIO: clean up control flow in kvm_vfio_file_add() Carlos López
2026-03-13 12:20 ` [PATCH 2/4] KVM: VFIO: use mutex guard in kvm_vfio_file_set_spapr_tce() Carlos López
2026-04-07 3:48 ` kernel test robot
2026-04-17 10:05 ` Carlos López
2026-04-17 13:31 ` Sean Christopherson [this message]
2026-03-13 12:20 ` [PATCH 3/4] KVM: VFIO: deduplicate file release logic Carlos López
2026-03-13 12:20 ` [PATCH 4/4] KVM: VFIO: update coherency only if file was deleted Carlos López
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=aeI2JCLldUFff0Q0@google.com \
--to=seanjc@google.com \
--cc=alex.williamson@redhat.com \
--cc=clopez@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox