All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>, kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: Re: [linux-next:master 4044/9592] arch/arm/kernel/ftrace.c:229:6: warning: no previous prototype for function 'prepare_ftrace_return'
Date: Wed, 2 Mar 2022 14:35:41 +0800	[thread overview]
Message-ID: <2db6ea89-846a-8d4e-a5c3-954411332029@intel.com> (raw)
In-Reply-To: <CAMj1kXEhEUbiS1QcbAd2+6vg2gWoqYwoDhmxPb1r1GVerjTOTA@mail.gmail.com>



On 3/2/2022 2:15 PM, Ard Biesheuvel wrote:
> (cc Rong Chen)
> 
> On Wed, 2 Mar 2022 at 03:52, kernel test robot <lkp@intel.com> wrote:
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   e6ada6df471f847da3b09b357e246c62335bc0bb
>> commit: 41918ec82eb6f80c8b401422f27ca76c85aa0cb7 [4044/9592] ARM: ftrace: enable the graph tracer with the EABI unwinder
>> config: arm-bcm2835_defconfig (https://download.01.org/0day-ci/archive/20220302/202203020913.I6LbmH7l-lkp@intel.com/config)
>> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d271fc04d5b97b12e6b797c6067d3c96a8d7470e)
>> 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 arm cross compiling tool for clang build
>>          # apt-get install binutils-arm-linux-gnueabi
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=41918ec82eb6f80c8b401422f27ca76c85aa0cb7
>>          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 41918ec82eb6f80c8b401422f27ca76c85aa0cb7
>>          # 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=arm SHELL=/bin/bash arch/arm/kernel/
>>
>> 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/arm/kernel/ftrace.c:229:6: warning: no previous prototype for function 'prepare_ftrace_return' [-Wmissing-prototypes]
>>     void prepare_ftrace_return(unsigned long *parent, unsigned long self_addr,
>>          ^
>>     arch/arm/kernel/ftrace.c:229:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
>>     void prepare_ftrace_return(unsigned long *parent, unsigned long self_addr,
>>     ^
>>     static
>>     1 warning generated.
>>
> 
> This function is asmlinkage so why is this still being reported?

Hi Ard,

Thanks for the information, we only checked 'asmlinkage' from warning 
messages:

   >>>> arch/arm/kernel/ftrace.c:229:6: warning: no previous prototype 
for function 'prepare_ftrace_return' [-Wmissing-prototypes]
 >>     void prepare_ftrace_return(unsigned long *parent, unsigned long 
self_addr,

but actually 'asmlinkage' is in another line:

    asmlinkage
    void prepare_ftrace_return(unsigned long *parent, unsigned long 
self_addr,

we missed this kind of problem, I'll take a look at it.

Best Regards,
Rong Chen

      reply	other threads:[~2022-03-02  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02  2:52 [linux-next:master 4044/9592] arch/arm/kernel/ftrace.c:229:6: warning: no previous prototype for function 'prepare_ftrace_return' kernel test robot
2022-03-02  6:15 ` Ard Biesheuvel
2022-03-02  6:15   ` Ard Biesheuvel
2022-03-02  6:35   ` Chen, Rong A [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=2db6ea89-846a-8d4e-a5c3-954411332029@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=ardb@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.