From: kernel test robot <lkp@intel.com>
To: Liu Chao <liuchao173@huawei.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, lixiaokeng@huawei.com, caihe@huawei.com
Subject: Re: [PATCH] Add interface to trigger backtrace on specified CPUs
Date: Wed, 13 Nov 2024 20:40:34 +0800 [thread overview]
Message-ID: <202411132038.ZTErSl6v-lkp@intel.com> (raw)
In-Reply-To: <20241112125609.1406586-1-liuchao173@huawei.com>
Hi Liu,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-nonmm-unstable]
[also build test ERROR on linus/master v6.12-rc7 next-20241113]
[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/Liu-Chao/Add-interface-to-trigger-backtrace-on-specified-CPUs/20241112-210050
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
patch link: https://lore.kernel.org/r/20241112125609.1406586-1-liuchao173%40huawei.com
patch subject: [PATCH] Add interface to trigger backtrace on specified CPUs
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20241113/202411132038.ZTErSl6v-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241113/202411132038.ZTErSl6v-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/202411132038.ZTErSl6v-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/backtrace.c:29:19: error: 'no_llseek' undeclared here (not in a function); did you mean 'noop_llseek'?
29 | .llseek = no_llseek,
| ^~~~~~~~~
| noop_llseek
vim +29 kernel/backtrace.c
25
26 static const struct file_operations backtrace_fops = {
27 .owner = THIS_MODULE,
28 .write = backtrace_write,
> 29 .llseek = no_llseek,
30 };
31
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-13 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 12:56 [PATCH] Add interface to trigger backtrace on specified CPUs Liu Chao
2024-11-13 12:40 ` kernel test robot [this message]
2024-11-13 14:03 ` 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=202411132038.ZTErSl6v-lkp@intel.com \
--to=lkp@intel.com \
--cc=caihe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuchao173@huawei.com \
--cc=lixiaokeng@huawei.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.