From: kernel test robot <lkp@intel.com>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, yujie.liu@intel.com, Baoquan He <bhe@redhat.com>,
linux-parisc@vger.kernel.org, llvm@lists.linux.dev,
kexec@lists.infradead.org, nathan@kernel.org,
oe-kbuild-all@lists.linux.dev, joe@perches.com,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/7] kexec_file, arm64: print out debugging message if required
Date: Sun, 26 Nov 2023 05:26:14 +0800 [thread overview]
Message-ID: <202311260548.1HaxcDnE-lkp@intel.com> (raw)
In-Reply-To: <20231124033642.520686-5-bhe@redhat.com>
Hi Baoquan,
kernel test robot noticed the following build errors:
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on tip/x86/core powerpc/next powerpc/fixes linus/master v6.7-rc2 next-20231124]
[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/Baoquan-He/kexec_file-add-kexec_file-flag-to-control-debug-printing/20231124-113942
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
patch link: https://lore.kernel.org/r/20231124033642.520686-5-bhe%40redhat.com
patch subject: [PATCH v2 4/7] kexec_file, arm64: print out debugging message if required
config: arm64-randconfig-001-20231126 (https://download.01.org/0day-ci/archive/20231126/202311260548.1HaxcDnE-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231126/202311260548.1HaxcDnE-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/202311260548.1HaxcDnE-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/arm64/kernel/machine_kexec.c:35:2: error: implicit declaration of function 'kexec_dprintk' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
kexec_dprintk("%s:%d:\n", func, line);
^
1 error generated.
vim +/kexec_dprintk +35 arch/arm64/kernel/machine_kexec.c
27
28 /**
29 * kexec_image_info - For debugging output.
30 */
31 #define kexec_image_info(_i) _kexec_image_info(__func__, __LINE__, _i)
32 static void _kexec_image_info(const char *func, int line,
33 const struct kimage *kimage)
34 {
> 35 kexec_dprintk("%s:%d:\n", func, line);
36 kexec_dprintk(" kexec kimage info:\n");
37 kexec_dprintk(" type: %d\n", kimage->type);
38 kexec_dprintk(" head: %lx\n", kimage->head);
39 kexec_dprintk(" kern_reloc: %pa\n", &kimage->arch.kern_reloc);
40 kexec_dprintk(" el2_vectors: %pa\n", &kimage->arch.el2_vectors);
41 }
42
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-25 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 3:36 [PATCH v2 0/7] kexec_file: print out debugging message if required Baoquan He
2023-11-24 3:36 ` [PATCH v2 1/7] kexec_file: add kexec_file flag to control debug printing Baoquan He
2023-11-24 3:36 ` [PATCH v2 2/7] kexec_file: print out debugging message if required Baoquan He
2023-11-24 7:16 ` Joe Perches
2023-11-24 8:40 ` Baoquan He
2023-11-24 3:36 ` [PATCH v2 3/7] kexec_file, x86: " Baoquan He
2023-11-24 3:36 ` [PATCH v2 4/7] kexec_file, arm64: " Baoquan He
2023-11-25 21:26 ` kernel test robot [this message]
2023-11-26 11:55 ` Baoquan He
2023-11-24 3:36 ` [PATCH v2 5/7] kexec_file, ricv: " Baoquan He
2023-11-24 3:36 ` [PATCH v2 6/7] kexec_file, power: " Baoquan He
2023-11-24 3:36 ` [PATCH v2 7/7] kexec_file, parisc: " Baoquan He
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=202311260548.1HaxcDnE-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=joe@perches.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.org \
--cc=yujie.liu@intel.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 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).