From: kernel test robot <lkp@intel.com>
To: Prasad Sodagudi <psodagud@codeaurora.org>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org,
Elliot Berman <eberman@codeaurora.org>
Subject: [ammarfaizi2-block:google/android/kernel/common/android12-5.10-2022-01 129/9999] drivers/android/debug_symbols.c:11:10: fatal error: asm/stacktrace.h: No such file or directory
Date: Sat, 12 Mar 2022 21:48:18 +0800 [thread overview]
Message-ID: <202203122107.sTzN2ohn-lkp@intel.com> (raw)
Hi Prasad,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android12-5.10-2022-01
head: d262b276948e382dbaa38474845bac692bae4236
commit: 3fcbb15c1a91a318fb9367bee24603af24648a2d [129/9999] ANDROID: android: Create debug_symbols driver
config: microblaze-allyesconfig (https://download.01.org/0day-ci/archive/20220312/202203122107.sTzN2ohn-lkp@intel.com/config)
compiler: microblaze-linux-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://github.com/ammarfaizi2/linux-block/commit/3fcbb15c1a91a318fb9367bee24603af24648a2d
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android12-5.10-2022-01
git checkout 3fcbb15c1a91a318fb9367bee24603af24648a2d
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=microblaze SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/android/debug_symbols.c:11:10: fatal error: asm/stacktrace.h: No such file or directory
11 | #include <asm/stacktrace.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
vim +11 drivers/android/debug_symbols.c
2
3 /*
4 * Copyright (c) 2021, The Linux Foundation. All rights reserved.
5 */
6
7 #include <linux/types.h>
8 #include <linux/kernel.h>
9 #include <linux/module.h>
10 #include <linux/android_debug_symbols.h>
> 11 #include <asm/stacktrace.h>
12 #include <asm/sections.h>
13
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-12 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202203122107.sTzN2ohn-lkp@intel.com \
--to=lkp@intel.com \
--cc=eberman@codeaurora.org \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psodagud@codeaurora.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