From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: Versatile QEMU broken in -next
Date: Sun, 2 May 2010 13:58:12 +0200 [thread overview]
Message-ID: <l2j63386a3d1005020458ta5e946bbke0ef56b9ed700ca2@mail.gmail.com> (raw)
In-Reply-To: <20100502100030.GA26601@debian>
2010/5/2 Rabin Vincent <rabin@rab.in>:
> On Sun, May 02, 2010 at 03:01:48AM +0200, Linus Walleij wrote:
>> Notice: I have no Versatile board, so I cannot know
>> if it breaks on the actual hardware. I only know it
>> breaks in QEMU. I don't know why though.
>>
>> I guess these all work nicely on a real board, so
>> I suspect it's a case of "QEMU needs to emulate
>> better", no real bug on real hardware.
>
> http://www.mail-archive.com/qemu-devel at nongnu.org/msg30785.html
Hey that's swift action Rabin, thanks a lot!
Yours,
Linus Walleij
prev parent reply other threads:[~2010-05-02 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 1:01 Versatile QEMU broken in -next Linus Walleij
2010-05-02 9:55 ` Russell King - ARM Linux
2010-05-02 10:00 ` Rabin Vincent
2010-05-02 11:58 ` Linus Walleij [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=l2j63386a3d1005020458ta5e946bbke0ef56b9ed700ca2@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).