LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: John Donnelly <john.d@servergy.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: 3.16.6 build error: swsusp_booke.S:85: Error: invalid sprg number
Date: Wed, 19 Mar 2014 23:52:19 -0500	[thread overview]
Message-ID: <1395291139.12479.315.camel@snotra.buserror.net> (raw)
In-Reply-To: <CAGtOQbTgXnxEHfuqtQ-BwpsnY=J2WktMFTNXysfYw9-cYprstQ@mail.gmail.com>

On Wed, 2014-03-19 at 17:58 -0500, John Donnelly wrote:
> Platform: Freescale  p4080--e500mc  ,
> 
> 
> Suggestions welcome . 
> 
> 
>  /bin/sh arch/powerpc/kernel/systbl_chk.sh
> arch/powerpc/kernel/systbl_chk.i
> make -f scripts/Makefile.build obj=arch/powerpc/kernel/vdso32
>   gcc -mbig-endian -m32 -Wp,-MD,arch/powerpc/kernel/.swsusp_booke.o.d
>  -nostdinc -isystem /usr/lib/gcc/ppc64-redhat-linux/4.8.2/include
> -I/root/linux-3.13.6/arch/powerpc/include
> -Iarch/powerpc/include/generated  -Iinclude
> -I/root/linux-3.13.6/arch/powerpc/include/uapi
> -Iarch/powerpc/include/generated/uapi
> -I/root/linux-3.13.6/include/uapi -Iinclude/generated/uapi
> -include /root/linux-3.13.6/include/linux/kconfig.h -D__KERNEL__
> -Iarch/powerpc  -D__ASSEMBLY__ -Iarch/powerpc  -gdwarf-2          -c
> -o arch/powerpc/kernel/swsusp_booke.o
> arch/powerpc/kernel/swsusp_booke.S
> arch/powerpc/kernel/swsusp_booke.S: Assembler messages:
> arch/powerpc/kernel/swsusp_booke.S:85: Error: invalid sprg number
> arch/powerpc/kernel/swsusp_booke.S:87: Error: invalid sprg number
> 
You need commit b58a7bd6df7b61446b833a7c72f8a1f11066e0b0.

-Scott

      reply	other threads:[~2014-03-20  4:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 22:58 3.16.6 build error: swsusp_booke.S:85: Error: invalid sprg number John Donnelly
2014-03-20  4:52 ` Scott Wood [this message]

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=1395291139.12479.315.camel@snotra.buserror.net \
    --to=scottwood@freescale.com \
    --cc=john.d@servergy.com \
    --cc=linuxppc-dev@lists.ozlabs.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