From: kernel test robot <lkp@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>, Tony Luck <tony.luck@intel.com>
Subject: [intel-tdx:guest-upstream 29/37] arch/x86/mm/mem_encrypt.c:96:13: warning: no previous prototype for 'mem_encrypt_init'
Date: Wed, 17 Nov 2021 21:30:40 +0800 [thread overview]
Message-ID: <202111172129.2yMYY42h-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]
tree: https://github.com/intel/tdx.git guest-upstream
head: 6d174fafe2becc43fd3eaebd3112a5a271b82ded
commit: 3a38521c8205c1c951e57551558dbfec739516cd [29/37] x86/tdx: Make pages shared in ioremap()
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/intel/tdx/commit/3a38521c8205c1c951e57551558dbfec739516cd
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest-upstream
git checkout 3a38521c8205c1c951e57551558dbfec739516cd
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/mm/mem_encrypt.c:96:13: warning: no previous prototype for 'mem_encrypt_init' [-Wmissing-prototypes]
96 | void __init mem_encrypt_init(void)
| ^~~~~~~~~~~~~~~~
vim +/mem_encrypt_init +96 arch/x86/mm/mem_encrypt.c
446571d51af2609 Kirill A. Shutemov 2020-03-18 94
446571d51af2609 Kirill A. Shutemov 2020-03-18 95 /* Architecture __weak replacement functions */
446571d51af2609 Kirill A. Shutemov 2020-03-18 @96 void __init mem_encrypt_init(void)
446571d51af2609 Kirill A. Shutemov 2020-03-18 97 {
446571d51af2609 Kirill A. Shutemov 2020-03-18 98 if (!sme_me_mask)
446571d51af2609 Kirill A. Shutemov 2020-03-18 99 return;
446571d51af2609 Kirill A. Shutemov 2020-03-18 100
446571d51af2609 Kirill A. Shutemov 2020-03-18 101 /* Call into SWIOTLB to update the SWIOTLB DMA buffers */
446571d51af2609 Kirill A. Shutemov 2020-03-18 102 swiotlb_update_mem_attributes();
446571d51af2609 Kirill A. Shutemov 2020-03-18 103
446571d51af2609 Kirill A. Shutemov 2020-03-18 104 print_amd_mem_encrypt_feature_info();
446571d51af2609 Kirill A. Shutemov 2020-03-18 105 }
446571d51af2609 Kirill A. Shutemov 2020-03-18 106
:::::: The code at line 96 was first introduced by commit
:::::: 446571d51af2609e66067b08442c89c5afd07843 x86: Move common memory encryption code to mem_encrypt.c
:::::: TO: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
:::::: CC: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65323 bytes --]
reply other threads:[~2021-11-17 13:31 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=202111172129.2yMYY42h-lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tony.luck@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