All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Zheng Zengkai <zhengzengkai@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 2430/2430] arch/arm64/mm/quick_kexec.c:21:13: warning: no previous prototype for 'reserve_quick_kexec'
Date: Sun, 1 Dec 2024 15:25:18 +0800	[thread overview]
Message-ID: <202412011507.pSC7pXCi-lkp@intel.com> (raw)

Hi Kefeng,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://gitee.com/openeuler/kernel.git OLK-5.10
head:   a2b4d661a5ca59dd7cf972c1cce8b98422102ab7
commit: d61f4ca086e99bb481961b1120e10e7a4296c392 [2430/2430] arm64: quick_kexec: Move to stand-alone file
config: arm64-randconfig-003-20241114 (https://download.01.org/0day-ci/archive/20241201/202412011507.pSC7pXCi-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241201/202412011507.pSC7pXCi-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412011507.pSC7pXCi-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/arm64/mm/quick_kexec.c:21:13: warning: no previous prototype for 'reserve_quick_kexec' [-Wmissing-prototypes]
      21 | void __init reserve_quick_kexec(void)
         |             ^~~~~~~~~~~~~~~~~~~
>> arch/arm64/mm/quick_kexec.c:47:13: warning: no previous prototype for 'request_quick_kexec_res' [-Wmissing-prototypes]
      47 | void __init request_quick_kexec_res(struct resource *res)
         |             ^~~~~~~~~~~~~~~~~~~~~~~


vim +/reserve_quick_kexec +21 arch/arm64/mm/quick_kexec.c

    20	
  > 21	void __init reserve_quick_kexec(void)
    22	{
    23		unsigned long long mem_start, mem_len;
    24	
    25		mem_len = quick_kexec_res.end;
    26		if (mem_len == 0)
    27			return;
    28	
    29		/* Current arm64 boot protocol requires 2MB alignment */
    30		mem_start = memblock_find_in_range(0, arm64_dma_phys_limit,
    31				mem_len, SZ_2M);
    32		if (mem_start == 0) {
    33			pr_warn("cannot allocate quick kexec mem (size:0x%llx)\n",
    34				mem_len);
    35			quick_kexec_res.end = 0;
    36			return;
    37		}
    38	
    39		memblock_reserve(mem_start, mem_len);
    40		pr_info("quick kexec mem reserved: 0x%016llx - 0x%016llx (%lld MB)\n",
    41			mem_start, mem_start + mem_len,	mem_len >> 20);
    42	
    43		quick_kexec_res.start = mem_start;
    44		quick_kexec_res.end = mem_start + mem_len - 1;
    45	}
    46	
  > 47	void __init request_quick_kexec_res(struct resource *res)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-12-01  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  7:25 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-13 19:31 [openeuler:OLK-5.10 2430/2430] arch/arm64/mm/quick_kexec.c:21:13: warning: no previous prototype for 'reserve_quick_kexec' 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=202412011507.pSC7pXCi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=zhengzengkai@huawei.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 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.