public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: arch/arm/boot/compressed/fdt_check_mem_start.c:62:10: warning: no previous prototype for 'fdt_check_mem_start'
Date: Wed, 10 Nov 2021 08:38:43 +0800	[thread overview]
Message-ID: <202111100840.gaI6caTo-lkp@intel.com> (raw)

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

Hi Geert,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   cb690f5238d71f543f4ce874aa59237cf53a877c
commit: 0673cb38951215060d7993b43ad3c45cd413c2c3 ARM: 9045/1: uncompress: Validate start of physical memory against passed DTB
date:   9 months ago
config: arm-randconfig-r022-20210927 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
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
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0673cb38951215060d7993b43ad3c45cd413c2c3
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 0673cb38951215060d7993b43ad3c45cd413c2c3
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross 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 >>):

>> arch/arm/boot/compressed/fdt_check_mem_start.c:62:10: warning: no previous prototype for 'fdt_check_mem_start' [-Wmissing-prototypes]
      62 | uint32_t fdt_check_mem_start(uint32_t mem_start, const void *fdt)
         |          ^~~~~~~~~~~~~~~~~~~


vim +/fdt_check_mem_start +62 arch/arm/boot/compressed/fdt_check_mem_start.c

    46	
    47	/*
    48	 * Check the start of physical memory
    49	 *
    50	 * Traditionally, the start address of physical memory is obtained by masking
    51	 * the program counter.  However, this does require that this address is a
    52	 * multiple of 128 MiB, precluding booting Linux on platforms where this
    53	 * requirement is not fulfilled.
    54	 * Hence validate the calculated address against the memory information in the
    55	 * DTB, and, if out-of-range, replace it by the real start address.
    56	 * To preserve backwards compatibility (systems reserving a block of memory
    57	 * at the start of physical memory, kdump, ...), the traditional method is
    58	 * always used if it yields a valid address.
    59	 *
    60	 * Return value: start address of physical memory to use
    61	 */
  > 62	uint32_t fdt_check_mem_start(uint32_t mem_start, const void *fdt)

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

             reply	other threads:[~2021-11-10  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  0:38 kernel test robot [this message]
2021-11-10  9:36 ` arch/arm/boot/compressed/fdt_check_mem_start.c:62:10: warning: no previous prototype for 'fdt_check_mem_start' Geert Uytterhoeven
2021-11-11  5:43   ` [kbuild-all] " Chen, Rong A
  -- strict thread matches above, loose matches on Subject: below --
2021-09-27 23:12 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=202111100840.gaI6caTo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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