linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jing Liu <jing2.liu@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Yang Zhong <yang.zhong@intel.com>
Subject: [linux-next:master 11041/12034] arch/x86/include/asm/fpu/api.h:135:46: sparse: sparse: marked inline, but without a definition
Date: Wed, 12 Jan 2022 22:58:06 +0800	[thread overview]
Message-ID: <202201122237.8fnwBZxc-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   32ce2abb03cfae17a9eb42bd6b1b619b72f23f20
commit: 445ecdf79be0c71ca248f7611aeefceaea3ec59f [11041/12034] kvm: x86: Exclude unpermitted xfeatures at KVM_GET_SUPPORTED_CPUID
config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20220112/202201122237.8fnwBZxc-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=445ecdf79be0c71ca248f7611aeefceaea3ec59f
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 445ecdf79be0c71ca248f7611aeefceaea3ec59f
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/kvm/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
   arch/x86/kvm/cpuid.c: note: in included file (through arch/x86/include/asm/pgtable.h, include/linux/pgtable.h, include/linux/mm.h, ...):
>> arch/x86/include/asm/fpu/api.h:135:46: sparse: sparse: marked inline, but without a definition

vim +135 arch/x86/include/asm/fpu/api.h

a0ff0611c2fbde Thomas Gleixner 2021-10-15  134  
980fe2fddcff21 Thomas Gleixner 2022-01-05 @135  extern inline u64 xstate_get_guest_group_perm(void);
980fe2fddcff21 Thomas Gleixner 2022-01-05  136  

:::::: The code at line 135 was first introduced by commit
:::::: 980fe2fddcff21937c93532b4597c8ea450346c1 x86/fpu: Extend fpu_xstate_prctl() with guest permissions

:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Paolo Bonzini <pbonzini@redhat.com>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


                 reply	other threads:[~2022-01-12 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202201122237.8fnwBZxc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jing2.liu@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=pbonzini@redhat.com \
    --cc=yang.zhong@intel.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