public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: linux-next: Tree for October 26
Date: Mon, 26 Oct 2009 15:57:19 +0800	[thread overview]
Message-ID: <1256543839.30470.29.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <a8e1da0910260053r245ee675yca4dc984303187df@mail.gmail.com>

Sorry, this should be turned off for x86_32. I will fix this.

Best Regards,
Huang Ying

On Mon, 2009-10-26 at 15:53 +0800, Dave Young wrote: 
> On Mon, Oct 26, 2009 at 3:50 PM, Dave Young <hidave.darkstar@gmail.com> wrote:
> > Hi,
> >
> > build fails with ghash ghash-clmulni-intel_asm.S:
> 
> It is a x86_32 laptop
> 
> 
> >
> >  AS      arch/x86/crypto/ghash-clmulni-intel_asm.o
> > arch/x86/crypto/ghash-clmulni-intel_asm.S: Assembler messages:
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:100: Error: bad register name `%rdi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:101: Error: bad register name `%rsi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:106: Error: bad register name `%rdi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:114: Error: bad register name `%rdx'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:117: Error: bad register name `%rdi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:118: Error: bad register name `%rcx)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:122: Error: bad register name `%rsi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:126: Error: bad register name `%rdx'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:127: Error: bad register name `%rsi'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:128: Error: bad register name `%rdx'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:131: Error: bad register name `%rdi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:142: Error: bad register name `%rsi)'
> > arch/x86/crypto/ghash-clmulni-intel_asm.S:156: Error: bad register name `%rdi)'
> > make[2]: *** [arch/x86/crypto/ghash-clmulni-intel_asm.o] Error 1
> > make[1]: *** [arch/x86/crypto] Error 2
> > make: *** [arch/x86] Error 2
> > make: *** Waiting for unfinished jobs....
> >
> > cc herbert & huang ying
> >
> > --
> > Regards
> > dave
> >
> 
> 
> 

  reply	other threads:[~2009-10-26  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  6:21 linux-next: Tree for October 26 Stephen Rothwell
2009-10-26  7:50 ` Dave Young
2009-10-26  7:53   ` Dave Young
2009-10-26  7:57     ` Huang Ying [this message]
2009-10-26 15:43 ` linux-next: Tree for October 26 (gfs2) Randy Dunlap
2009-10-26 16:00   ` Steven Whitehouse
2009-10-26 22:09 ` [PATCH -next] netxen: fix builds for SYSFS=n or MODULES=n Randy Dunlap
2009-10-27 22:09   ` Dhananjay Phadke
2009-10-28  9:34     ` David Miller
2009-10-28  9:36   ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2010-10-26  3:06 linux-next: Tree for October 26 Stephen Rothwell

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=1256543839.30470.29.camel@yhuang-dev.sh.intel.com \
    --to=ying.huang@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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