linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] ppc32: Fix compile of sha1-powerpc-asm.S
Date: Wed, 6 Mar 2013 15:09:50 +1100	[thread overview]
Message-ID: <20130306040950.GC3493@concordia> (raw)
In-Reply-To: <alpine.DEB.2.10.1303041656010.22410@trent.utfs.org>

On Mon, Mar 04, 2013 at 05:23:14PM -0800, Christian Kujau wrote:
> On Tue, 26 Feb 2013 at 13:20, Tony Breeds wrote:
> > When building with CRYPTO_SHA1_PPC enabled we fail with:
> > ---
> > powerpc/crypto/sha1-powerpc-asm.S: Assembler messages:
> > powerpc/crypto/sha1-powerpc-asm.S:116: Error: can't resolve `0' {*ABS* section} - `STACKFRAMESIZE' {*UND* section}
> > powerpc/crypto/sha1-powerpc-asm.S:116: Error: expression too complex
> > powerpc/crypto/sha1-powerpc-asm.S:178: Error: unsupported relocation against STACKFRAMESIZE
> > ---
> > 
> > Use INT_FRAME_SIZE instead.
> > 
> > Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
> 
> Thanks for the fix! Ran into this as well, with your patch 3.9-rc1 
> compiles again (and it even boots :-))
> 
> Tested-by: Christian Kujau <lists@nerdbynature.de>
> 
> $ grep -A10 sha1 /proc/crypto
> name         : sha1
> driver       : sha1-powerpc
> module       : kernel
> priority     : 0
> refcnt       : 1
> selftest     : passed
> type         : shash
> blocksize    : 64
> digestsize   : 20

Thanks Christian. What hardware are you on?

cheers

  reply	other threads:[~2013-03-06  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  2:20 [PATCH] ppc32: Fix compile of sha1-powerpc-asm.S Tony Breeds
2013-03-05  1:23 ` Christian Kujau
2013-03-06  4:09   ` Michael Ellerman [this message]
2013-03-06  6:42     ` Christian Kujau

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=20130306040950.GC3493@concordia \
    --to=michael@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lists@nerdbynature.de \
    /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).