From: Davidlohr Bueso <dave@stgolabs.net>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
Davidlohr Bueso <dbueso@suse.de>,
peterz@infradead.org, will@kernel.org, bigeasy@linutronix.de,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
linux-mips@vger.kernel.org, Paul Mackerras <paulus@ozlabs.org>,
joel@joelfernandes.org, pbonzini@redhat.com, tglx@linutronix.de,
torvalds@linux-foundation.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 3/4] kvm: Replace vcpu->swait with rcuwait
Date: Tue, 24 Mar 2020 10:56:14 -0700 [thread overview]
Message-ID: <20200324175614.fzwutnpw2xiigqni@linux-p48b> (raw)
In-Reply-To: <202003250014.iSvLXrUS%lkp@intel.com>
On Wed, 25 Mar 2020, kbuild test robot wrote:
> arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_block':
>>> arch/x86/kvm/../../../virt/kvm/kvm_main.c:2698:16: error: macro "rcuwait_wait_event" passed 3 arguments, but takes just 2
> TASK_IDLE);
This is because this series relies on the rcuwait change:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=locking/core&id=80fbaf1c3f2926c834f8ca915441dfe27ce5487e
Thanks,
Davidlohr
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-03-24 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200324044453.15733-1-dave@stgolabs.net>
2020-03-24 4:44 ` [PATCH 3/4] kvm: Replace vcpu->swait with rcuwait Davidlohr Bueso
2020-03-24 12:07 ` kbuild test robot
2020-03-24 16:47 ` kbuild test robot
2020-03-24 17:56 ` Davidlohr Bueso [this message]
2020-03-25 17:09 ` Paolo Bonzini
2020-04-14 21:12 ` Davidlohr Bueso
2020-04-15 12:11 ` Paolo Bonzini
2020-04-20 16:41 ` [PATCH v2] " Davidlohr Bueso
2020-04-20 17:12 ` Marc Zyngier
2020-04-20 17:25 ` Paolo Bonzini
2020-04-20 20:56 ` Davidlohr Bueso
2020-04-20 21:04 ` Paolo Bonzini
2020-04-20 21:50 ` Davidlohr Bueso
2020-04-21 9:43 ` Paolo Bonzini
2020-04-21 18:07 ` Davidlohr Bueso
2020-04-21 19:52 ` Paolo Bonzini
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=20200324175614.fzwutnpw2xiigqni@linux-p48b \
--to=dave@stgolabs.net \
--cc=bigeasy@linutronix.de \
--cc=dbueso@suse.de \
--cc=joel@joelfernandes.org \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).