linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Rong Chen <rong.a.chen@intel.com>
Cc: kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] Re: [ardb:for-kernelci 25/25] arch/arm/kernel/traps.c:865:17: warning: no previous prototype for function 'handle_bad_stack'
Date: Thu, 2 Dec 2021 08:53:13 +0100	[thread overview]
Message-ID: <CAMj1kXFKYX+XsojJGzYZryHht=CV-7-R+aNXaSO9zabunXYNqg@mail.gmail.com> (raw)
In-Reply-To: <a03e765d-c22a-3bd8-8d94-36966b91dc2c@intel.com>

On Thu, 2 Dec 2021 at 08:34, Rong Chen <rong.a.chen@intel.com> wrote:
>
>
>
> On 11/30/21 21:12, Ard Biesheuvel wrote:
> > On Thu, 25 Nov 2021 at 02:35, kernel test robot <lkp@intel.com> wrote:
> >> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git for-kernelci
> >> head:   5da04a8b7050432b72f6551b6c95e4b5b5fd68d1
> >> commit: 5da04a8b7050432b72f6551b6c95e4b5b5fd68d1 [25/25] ARM: implement THREAD_INFO_IN_TASK for uniprocessor systems
> >> config: arm-randconfig-r024-20211124 (https://download.01.org/0day-ci/archive/20211125/202111250918.ErFZktQF-lkp@intel.com/config)
> >> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 67a1c45def8a75061203461ab0060c75c864df1c)
> >> 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/ardb/linux.git/commit/?id=5da04a8b7050432b72f6551b6c95e4b5b5fd68d1
> >>          git remote add ardb git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git
> >>          git fetch --no-tags ardb for-kernelci
> >>          git checkout 5da04a8b7050432b72f6551b6c95e4b5b5fd68d1
> >>          # save the config file to linux build tree
> >>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm
> >>
> >> 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 >>):
> >>
> > This is yet another false positive. asmlinkage routines don't need a
> > prototype because they are called from assembler. This is not going to
> > get fixed, so please don't report this error anymore.
>
> Hi Ard,
>
> Sorry for the noise, we'll ignore the warnings in the future.
>

Thanks! And if at all possible, please extend this to all routines
marked as asmlinkage?

-- 
Ard.

  reply	other threads:[~2021-12-02  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25  1:34 [ardb:for-kernelci 25/25] arch/arm/kernel/traps.c:865:17: warning: no previous prototype for function 'handle_bad_stack' kernel test robot
2021-11-30 13:12 ` Ard Biesheuvel
2021-12-02  7:34   ` [kbuild-all] " Rong Chen
2021-12-02  7:53     ` Ard Biesheuvel [this message]
2021-12-02  8:03       ` Rong Chen

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='CAMj1kXFKYX+XsojJGzYZryHht=CV-7-R+aNXaSO9zabunXYNqg@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=rong.a.chen@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;
as well as URLs for NNTP newsgroup(s).