public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: [mark-rutland:arm64/entry/further-rework 3/6] arch/arm64/kernel/entry-common.c:203:17: warning: no previous prototype for function 'prepare_el0t_return_from_fork'
Date: Thu, 8 Jul 2021 08:05:21 +0800	[thread overview]
Message-ID: <202107080814.glfY2lWN-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/entry/further-rework
head:   0b26c84bfdad0505d4c64c47af300e988990cc03
commit: 7384b6c882f5c127950555c9fb64cada519f0ac3 [3/6] arm64: entry: add hooks for entry/exit work
config: arm64-randconfig-r026-20210707 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8d69635ed9ecf36fd0ca85906bfde17949671cbe)
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
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/commit/?id=7384b6c882f5c127950555c9fb64cada519f0ac3
        git remote add mark-rutland https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git
        git fetch --no-tags mark-rutland arm64/entry/further-rework
        git checkout 7384b6c882f5c127950555c9fb64cada519f0ac3
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64 

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/arm64/kernel/entry-common.c:203:17: warning: no previous prototype for function 'prepare_el0t_return_from_fork' [-Wmissing-prototypes]
   asmlinkage void prepare_el0t_return_from_fork(struct pt_regs *regs)
                   ^
   arch/arm64/kernel/entry-common.c:203:12: note: declare 'static' if the function is not intended to be used outside of this translation unit
   asmlinkage void prepare_el0t_return_from_fork(struct pt_regs *regs)
              ^
              static 
   1 warning generated.


vim +/prepare_el0t_return_from_fork +203 arch/arm64/kernel/entry-common.c

   202	
 > 203	asmlinkage void prepare_el0t_return_from_fork(struct pt_regs *regs)
   204	{
   205		__prepare_el0t_return(regs);
   206	}
   207	

---
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: 37000 bytes --]

             reply	other threads:[~2021-07-08  0:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  0:05 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-08  0:17 [mark-rutland:arm64/entry/further-rework 3/6] arch/arm64/kernel/entry-common.c:203:17: warning: no previous prototype for function 'prepare_el0t_return_from_fork' kernel test robot

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=202107080814.glfY2lWN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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