All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 29 (x86 posttest)
Date: Thu, 29 Oct 2009 12:48:12 -0400	[thread overview]
Message-ID: <4AE9C74C.2040309@redhat.com> (raw)
In-Reply-To: <20091029090627.7857ed08.rdunlap@xenotime.net>

Randy Dunlap wrote:
> On Thu, 29 Oct 2009 18:29:19 +1100 Stephen Rothwell wrote:
>
>> Hi all,
>>
>> [I accidentally deleted my merge log today, so sorry to anyone who
>> actually reads them :-), the summary still appears below.]
>
>
> I'm getting this on x86_64:
>
>    TEST    posttest
> Error: ffffffff810299e2:	f2 41 0f 28 52 b0    	repnz movaps -0x50(%r10),%xmm2
> Error: objdump says 6 bytes, but insn_get_length() says 4 (attr:0)
> make[2]: *** [posttest] Error 2

Ah, that's should be fixed by AVX support patch which I've posted.
http://git.kernel.org/tip/e0e492e99b372c6990a5daca9e4683c341f1330e

Thank you,


-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com

  reply	other threads:[~2009-10-29 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  7:29 linux-next: Tree for October 29 Stephen Rothwell
2009-10-29 16:06 ` linux-next: Tree for October 29 (x86 posttest) Randy Dunlap
2009-10-29 16:48   ` Masami Hiramatsu [this message]
2009-11-06 16:59     ` Randy Dunlap
2009-11-10  0:40       ` Masami Hiramatsu
2009-11-10  2:08         ` Stephen Rothwell
2009-11-10  4:55           ` Masami Hiramatsu
2009-10-29 16:52 ` [PATCH] staging: fix wireless drivers depends Randy Dunlap

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=4AE9C74C.2040309@redhat.com \
    --to=mhiramat@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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 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.