From: kernel test robot <lkp@intel.com>
To: Guo Weikang <guoweikang.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Sam Creasey <sammy@sammy.net>,
Huacai Chen <chenhuacai@kernel.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Oreoluwa Babatunde <quic_obabatun@quicinc.com>,
rafael.j.wysocki@intel.com, Palmer Dabbelt <palmer@rivosinc.com>,
Hanjun Guo <guohanjun@huawei.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Johannes Berg <johannes.berg@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
Christian Brauner <brauner@kernel.org>,
KP Singh <kpsingh@kernel.org>,
Richard Henderson <richard.henderson@linaro.org>,
Matt Turner <mattst88@gmail.com>,
Russell King <linux@armlinux.org.uk>,
WANG Xuerui <kernel@xen0n.name>,
Michael Ellerman <mpe@ellerman.id.au>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Stafford Horne <shorne@gmail.com>
Subject: Re: [PATCH v5] mm/memblock: Add memblock_alloc_or_panic interface
Date: Sun, 22 Dec 2024 12:28:59 +0800 [thread overview]
Message-ID: <202412221259.JuGNAUCq-lkp@intel.com> (raw)
In-Reply-To: <20241222030331.2704579-1-guoweikang.kernel@gmail.com>
Hi Guo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Guo-Weikang/mm-memblock-Add-memblock_alloc_or_panic-interface/20241222-110513
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20241222030331.2704579-1-guoweikang.kernel%40gmail.com
patch subject: [PATCH v5] mm/memblock: Add memblock_alloc_or_panic interface
config: arm-randconfig-002-20241222 (https://download.01.org/0day-ci/archive/20241222/202412221259.JuGNAUCq-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241222/202412221259.JuGNAUCq-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/202412221259.JuGNAUCq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/memblock.c:1706: warning: Function parameter or struct member 'func' not described in '__memblock_alloc_or_panic'
>> mm/memblock.c:1706: warning: Excess function parameter 'fuc' description in '__memblock_alloc_or_panic'
vim +1706 mm/memblock.c
1693
1694 /**
1695 * __memblock_alloc_or_panic - Try to allocate memory and panic on failure
1696 * @size: size of memory block to be allocated in bytes
1697 * @align: alignment of the region and block's size
1698 * @fuc: caller func name
1699 *
1700 * This function attempts to allocate memory using memblock_alloc,
1701 * and in case of failure, it calls panic with the formatted message.
1702 * This function should not be used directly, please use the macro memblock_alloc_or_panic.
1703 */
1704 void *__init __memblock_alloc_or_panic(phys_addr_t size, phys_addr_t align,
1705 const char *func)
> 1706 {
1707 void *addr = memblock_alloc(size, align);
1708
1709 if (unlikely(!addr))
1710 panic("%s: Failed to allocate %pap bytes\n", func, &size);
1711 return addr;
1712 }
1713
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-12-22 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 3:03 Guo Weikang
2024-12-22 4:28 ` kernel test robot [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=202412221259.JuGNAUCq-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=cl@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=dennis@kernel.org \
--cc=eahariha@linux.microsoft.com \
--cc=geert@linux-m68k.org \
--cc=guohanjun@huawei.com \
--cc=guoweikang.kernel@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kernel@xen0n.name \
--cc=kpsingh@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=mattst88@gmail.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.com \
--cc=quic_obabatun@quicinc.com \
--cc=rafael.j.wysocki@intel.com \
--cc=richard.henderson@linaro.org \
--cc=rppt@kernel.org \
--cc=sammy@sammy.net \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=tj@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox