From: Peter Zijlstra <peterz@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [peterz-queue:locking/core 17/19] arch/x86/kvm/x86.h:29:30: error: too many arguments to function call, expected 0, have 1
Date: Wed, 23 Mar 2022 15:45:22 +0100 [thread overview]
Message-ID: <YjsygpbbKmraVol9@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKwvOdnEyGLi14b0qsc2=aSRafCrQD-Zyh+Oq+E-vx+c1viErg@mail.gmail.com>
On Mon, Mar 21, 2022 at 10:51:29AM -0700, Nick Desaulniers wrote:
> On Fri, Mar 18, 2022 at 9:10 PM kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
> > head: 200a79c670d24d4d9a75a6a9cbfd14af2f5d0ad9
> > commit: 5c9f3806a4400c2957abeea9419547f856457a20 [17/19] lockdep: Fix -Wunused-parameter for _THIS_IP_
> > config: x86_64-randconfig-a014 (https://download.01.org/0day-ci/archive/20220319/202203191213.tC0sjaY7-lkp@intel.com/config)
> > compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a6e70e4056dff962ec634c5bd4f2f4105a0bef71)
> > reproduce (this is a W=1 build):
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=5c9f3806a4400c2957abeea9419547f856457a20
> > git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
> > git fetch --no-tags peterz-queue locking/core
> > git checkout 5c9f3806a4400c2957abeea9419547f856457a20
> > # save the config file to linux build tree
> > mkdir build_dir
> > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from arch/x86/kvm/x86.c:22:
> > In file included from arch/x86/kvm/mmu.h:7:
> > In file included from arch/x86/kvm/cpuid.h:5:
> > >> arch/x86/kvm/x86.h:29:30: error: too many arguments to function call, expected 0, have 1
> > lockdep_hardirqs_on_prepare(CALLER_ADDR0);
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
>
> Peter, I think you dropped the hunk to include/linux/kvm_host.h when
> applying this patch?
>
Someone moved that function to arch/x86/kvm/x86.h which is why it went
sideways when I resolved it. Should hopefully be fixed now, lemme go do
a few builds before I push out.
prev parent reply other threads:[~2022-03-23 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 4:09 [peterz-queue:locking/core 17/19] arch/x86/kvm/x86.h:29:30: error: too many arguments to function call, expected 0, have 1 kernel test robot
2022-03-21 17:51 ` Nick Desaulniers
2022-03-21 21:14 ` Peter Zijlstra
2022-03-23 14:45 ` Peter Zijlstra [this message]
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=YjsygpbbKmraVol9@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.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