All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linuxppc-dev@lists.ozlabs.org,
	Linux-Next <linux-next@vger.kernel.org>,
	yu.liu@freescale.com, stuart.yoder@freescale.com,
	Timur Tabi <timur@freescale.com>
Subject: Re: [-next] ERROR: "epapr_hypercall_start" [drivers/tty/ehv_bytechan.ko] undefined!
Date: Fri, 10 Aug 2012 18:58:58 +1000	[thread overview]
Message-ID: <1344589138.27290.18.camel@concordia> (raw)
In-Reply-To: <CAMuHMdV9dgjdHuz3avU1dubyekcZwT70x=5W+CL7iHQuoC1n_w@mail.gmail.com>

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>
    Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
    Signed-off-by: Alexander Graf <agraf@suse.de>



cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Next <linux-next@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org, stuart.yoder@freescale.com,
	yu.liu@freescale.com, Timur Tabi <timur@freescale.com>
Subject: Re: [-next] ERROR: "epapr_hypercall_start" [drivers/tty/ehv_bytechan.ko] undefined!
Date: Fri, 10 Aug 2012 18:58:58 +1000	[thread overview]
Message-ID: <1344589138.27290.18.camel@concordia> (raw)
In-Reply-To: <CAMuHMdV9dgjdHuz3avU1dubyekcZwT70x=5W+CL7iHQuoC1n_w@mail.gmail.com>

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>
    Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
    Signed-off-by: Alexander Graf <agraf@suse.de>



cheers

  reply	other threads:[~2012-08-10  8:58 UTC|newest]

Thread overview: 6+ 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 [this message]
2012-08-10  8:58   ` Michael Ellerman
2012-08-10  9:00   ` Michael Ellerman
2012-08-10 17:05     ` Scott Wood
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=1344589138.27290.18.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stuart.yoder@freescale.com \
    --cc=timur@freescale.com \
    --cc=yu.liu@freescale.com \
    /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.