From: Michael Ellerman <mpe@ellerman.id.au>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
sachinp <sachinp@linux.vnet.ibm.com>,
keith.busch@intel.com, bhelgaas@google.com
Subject: Re: [linux-next][bisected e3fbcc7c] build error at drivers/pci/pcie/aer_inject.c:444:6: error: ‘struct pt_regs’ has no member named ‘ip
Date: Tue, 09 Oct 2018 20:47:20 +1100 [thread overview]
Message-ID: <87woqr1mfr.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1539069292.17569.7.camel@abdul.in.ibm.com>
Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> Greeting's
>
> Today's linux-next fails to build on ppc with below error
>
> drivers/pci/pcie/aer_inject.c: In function ‘aer_inject_ftrace_thunk’:
> drivers/pci/pcie/aer_inject.c:444:6: error: ‘struct pt_regs’ has no
> member named ‘ip’
> regs->ip = (unsigned long) hook->function;
> ^
> make[3]: *** [drivers/pci/pcie/aer_inject.o] Error 1
> make[2]: *** [drivers/pci/pcie] Error 2
> make[1]: *** [drivers/pci] Error 2
>
> Machine: Power 9
> kernel version: 4.19.0-rc7-next-20181008
> gcc version: 4.8.5 20150623
> config attached
>
> Recent code changes from these commits:
>
> c79ad38b36dd4967d67f83fc48bade37ee041a47 PCI/AER: Abstract AER interrupt handling
> 7b23285f930a8dedcbf749661cd0f2cc27f79be6 PCI/AER: Reuse existing pcie_port_find_device() interface
> e3fbcc7c4b130f81ea586183db561fa3ce9c6447 PCI/AER: Covertly inject errors with ftrace hooks
I don't see this commit in today's linux next (20181009) so presumably
someone else has noticed and dropped the commit?
cheers
next prev parent reply other threads:[~2018-10-09 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 7:14 [linux-next][bisected e3fbcc7c] build error at drivers/pci/pcie/aer_inject.c:444:6: error: ‘struct pt_regs’ has no member named ‘ip Abdul Haleem
2018-10-09 9:47 ` Michael Ellerman [this message]
2018-10-09 10:40 ` Abdul Haleem
2018-10-09 12:17 ` Bjorn Helgaas
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=87woqr1mfr.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).