From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [-next] ERROR: "epapr_hypercall_start" [drivers/tty/ehv_bytechan.ko] undefined!
Date: Fri, 10 Aug 2012 12:05:07 -0500 [thread overview]
Message-ID: <50253F43.1070706@freescale.com> (raw)
In-Reply-To: <1344589252.27290.19.camel@concordia>
On 08/10/2012 04:00 AM, Michael Ellerman wrote:
> On Fri, 2012-08-10 at 18:58 +1000, Michael Ellerman wrote:
>> On Fri, 2012-08-10 at 09:43 +0200, Geert Uytterhoeven wrote:
>>> Sicne a few days, powerpc allmodconfig fails with:
>>>
>>> ERROR: "epapr_hypercall_start" [drivers/tty/ehv_bytechan.ko] undefined!
>>> make[2]: *** [__modpost] Error 1
>>> make[1]: *** [modules] Error 2
>>>
>>> http://kisskb.ellerman.id.au/kisskb/buildresult/6883300/
>>
>>
>> Yep, modular build is broken.
>>
>> Since this commit by the looks of it:
>>
>> commit 6d2d82627f4f1e96a33664ace494fa363e0495cb
>> Author: Liu Yu-B13201 <Yu.Liu@freescale.com>
>> Date: Tue Jul 3 05:48:56 2012 +0000
>>
>> PPC: Don't use hardcoded opcode for ePAPR hcall invocation
>>
>> Signed-off-by: Liu Yu <yu.liu@freescale.com>
>
> And this address bounces, nice.
He doesn't work here anymore. We'll take care of the breakage.
-Scott
next prev parent reply other threads:[~2012-08-10 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 7:43 [-next] ERROR: "epapr_hypercall_start" [drivers/tty/ehv_bytechan.ko] undefined! Geert Uytterhoeven
2012-08-10 8:58 ` Michael Ellerman
2012-08-10 9:00 ` Michael Ellerman
2012-08-10 17:05 ` Scott Wood [this message]
2012-08-11 4:21 ` Michael Ellerman
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=50253F43.1070706@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.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).