All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: arch/arm/kernel/traps.c:775:6: warning: no previous prototype for function 'abort'
Date: Thu, 9 Dec 2021 15:34:42 +0000	[thread overview]
Message-ID: <YbIiEqxPfbYr10pQ@shell.armlinux.org.uk> (raw)
In-Reply-To: <202112092330.MRS9Xygy-lkp@intel.com>

On Thu, Dec 09, 2021 at 11:22:48PM +0800, kernel test robot wrote:
> Hi Ard,
> 
> FYI, the error/warning still remains.

This is nothing new. You claim that the abort() warning newly shows up
as a result of a recent change, but I can most definitely assure you
that abort() has never had a prototype, and it's there because the
compiler can generate code that issues a branch to this function.

This can be seen in the blame output, which references the first commit
in the kernel tree for these lines.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

WARNING: multiple messages have this Message-ID (diff)
From: Russell King (Oracle) <linux@armlinux.org.uk>
To: kbuild-all@lists.01.org
Subject: Re: arch/arm/kernel/traps.c:775:6: warning: no previous prototype for function 'abort'
Date: Thu, 09 Dec 2021 15:34:42 +0000	[thread overview]
Message-ID: <YbIiEqxPfbYr10pQ@shell.armlinux.org.uk> (raw)
In-Reply-To: <202112092330.MRS9Xygy-lkp@intel.com>

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

On Thu, Dec 09, 2021 at 11:22:48PM +0800, kernel test robot wrote:
> Hi Ard,
> 
> FYI, the error/warning still remains.

This is nothing new. You claim that the abort() warning newly shows up
as a result of a recent change, but I can most definitely assure you
that abort() has never had a prototype, and it's there because the
compiler can generate code that issues a branch to this function.

This can be seen in the blame output, which references the first commit
in the kernel tree for these lines.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2021-12-09 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 15:22 arch/arm/kernel/traps.c:775:6: warning: no previous prototype for function 'abort' kernel test robot
2021-12-09 15:22 ` kernel test robot
2021-12-09 15:34 ` Russell King (Oracle) [this message]
2021-12-09 15:34   ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2021-11-04  8:48 kernel test robot
2021-11-04  8:48 ` kernel test robot
2021-07-13 10:38 kernel test robot
2021-07-13 10:38 ` 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=YbIiEqxPfbYr10pQ@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ardb@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    /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.