From: kernel test robot <lkp@intel.com>
To: Alexander Graf <graf@amazon.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
x86@kernel.org, Eric Biederman <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Rutland <mark.rutland@arm.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>,
James Gowans <jgowans@amazon.com>,
Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
arnd@arndb.de, pbonzini@redhat.com, madvenka@linux.microsoft.com,
Anthony Yznaga <anthony.yznaga@oracle.com>,
Usama Arif <usama.arif@bytedance.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH 06/15] arm64: Add KHO support
Date: Wed, 13 Dec 2023 21:41:10 +0800 [thread overview]
Message-ID: <202312132139.g2NKV67G-lkp@intel.com> (raw)
In-Reply-To: <20231213000452.88295-7-graf@amazon.com>
Hi Alexander,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[also build test WARNING on arm64/for-next/core akpm-mm/mm-everything linus/master v6.7-rc5 next-20231213]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Alexander-Graf/mm-memblock-Add-support-for-scratch-memory/20231213-080941
base: tip/x86/core
patch link: https://lore.kernel.org/r/20231213000452.88295-7-graf%40amazon.com
patch subject: [PATCH 06/15] arm64: Add KHO support
config: microblaze-randconfig-r133-20231213 (https://download.01.org/0day-ci/archive/20231213/202312132139.g2NKV67G-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231213/202312132139.g2NKV67G-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/202312132139.g2NKV67G-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/of/fdt.c:1012:13: sparse: sparse: symbol 'early_init_dt_check_kho' was not declared. Should it be static?
vim +/early_init_dt_check_kho +1012 drivers/of/fdt.c
1008
1009 /**
1010 * early_init_dt_check_kho - Decode info required for kexec handover from DT
1011 */
> 1012 void __init early_init_dt_check_kho(void)
1013 {
1014 #ifdef CONFIG_KEXEC_KHO
1015 unsigned long node = chosen_node_offset;
1016 u64 kho_start, scratch_start, scratch_size, mem_start, mem_size;
1017 const __be32 *p;
1018 int l;
1019
1020 if ((long)node < 0)
1021 return;
1022
1023 p = of_get_flat_dt_prop(node, "linux,kho-dt", &l);
1024 if (l != (dt_root_addr_cells + dt_root_size_cells) * sizeof(__be32))
1025 return;
1026
1027 kho_start = dt_mem_next_cell(dt_root_addr_cells, &p);
1028
1029 p = of_get_flat_dt_prop(node, "linux,kho-scratch", &l);
1030 if (l != (dt_root_addr_cells + dt_root_size_cells) * sizeof(__be32))
1031 return;
1032
1033 scratch_start = dt_mem_next_cell(dt_root_addr_cells, &p);
1034 scratch_size = dt_mem_next_cell(dt_root_addr_cells, &p);
1035
1036 p = of_get_flat_dt_prop(node, "linux,kho-mem", &l);
1037 if (l != (dt_root_addr_cells + dt_root_size_cells) * sizeof(__be32))
1038 return;
1039
1040 mem_start = dt_mem_next_cell(dt_root_addr_cells, &p);
1041 mem_size = dt_mem_next_cell(dt_root_addr_cells, &p);
1042
1043 kho_populate(kho_start, scratch_start, scratch_size, mem_start, mem_size);
1044 #endif
1045 }
1046
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-13 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231213000452.88295-7-graf@amazon.com>
2023-12-13 11:22 ` [PATCH 06/15] arm64: Add KHO support kernel test robot
2023-12-13 13:41 ` 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=202312132139.g2NKV67G-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=arnd@arndb.de \
--cc=ashish.kalra@amd.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=ebiederm@xmission.com \
--cc=graf@amazon.com \
--cc=hpa@zytor.com \
--cc=jgowans@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skinsburskii@linux.microsoft.com \
--cc=thomas.lendacky@amd.com \
--cc=usama.arif@bytedance.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).