From: kbuild test robot <lkp@intel.com>
To: Keith Busch <keith.busch@intel.com>
Cc: kbuild-all@01.org, linux-pci@vger.kernel.org,
Bjorn Helgaas <helgaas@kernel.org>
Subject: [pci:pci/hotplug 41/49] drivers/pci/pcie/aer_inject.c:458:6: error: 'struct pt_regs' has no member named 'ip'
Date: Mon, 8 Oct 2018 19:28:25 +0800 [thread overview]
Message-ID: <201810081923.62w2arIr%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/hotplug
head: ec7da63425d2d7ca40c03d71b966a0f9469b5ad3
commit: 857bcd7d2a219d4a7a1306ad200b2646cacbadae [41/49] PCI/AER: Covertly inject errors with ftrace hooks
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 857bcd7d2a219d4a7a1306ad200b2646cacbadae
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm
All errors (new ones prefixed by >>):
drivers/pci/pcie/aer_inject.c: In function 'aer_inject_ftrace_thunk':
>> drivers/pci/pcie/aer_inject.c:458:6: error: 'struct pt_regs' has no member named 'ip'
regs->ip = (unsigned long) hook->function;
^~
vim +458 drivers/pci/pcie/aer_inject.c
453
454 static void notrace aer_inject_ftrace_thunk(unsigned long ip, unsigned long parent_ip,
455 struct ftrace_ops *ops, struct pt_regs *regs)
456 {
457 struct aer_hook *hook = container_of(ops, struct aer_hook, ops);
> 458 regs->ip = (unsigned long) hook->function;
459 }
460
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67167 bytes --]
reply other threads:[~2018-10-08 11:28 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=201810081923.62w2arIr%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=helgaas@kernel.org \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.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).