From: Boaz Harrosh <bharrosh@panasas.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Amerigo Wang <xiyou.wangcong@gmail.com>,
Paul Menage <menage@google.com>,
akpm@linux-foundation.org, jdike@addtoit.com,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] UML: Fix some apparent bitrot
Date: Mon, 22 Jun 2009 15:05:52 +0300 [thread overview]
Message-ID: <4A3F73A0.1010005@panasas.com> (raw)
In-Reply-To: <20090622205226.fee30ba8.sfr@canb.auug.org.au>
On 06/22/2009 01:52 PM, Stephen Rothwell wrote:
> Hi Amerigo,
>
> On Mon, 22 Jun 2009 16:57:35 +0800 Amerigo Wang <xiyou.wangcong@gmail.com> wrote:
>> Stephan, could you please also do compiling tests for UML in your -next tree?
>>
>> Thanks!
>
> I would be happy to do this, all I need is for someone to tell me how to
> do this given we have PowerPC hosts so our X86 compilers are cross
> compilers.
OK I'm not sure how to do that?
But just a plain PowerPC UML could be nice for a start. If it at all
works.
Thanks
Boaz
next prev parent reply other threads:[~2009-06-22 12:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 0:55 [PATCH] UML: Fix some apparent bitrot Paul Menage
2009-06-22 2:46 ` Amerigo Wang
2009-06-24 12:23 ` [uml-devel] " Boaz Harrosh
2009-06-25 10:47 ` Amerigo Wang
2009-06-22 8:43 ` Boaz Harrosh
2009-06-22 8:57 ` Amerigo Wang
2009-06-22 10:52 ` Stephen Rothwell
2009-06-22 12:05 ` Boaz Harrosh [this message]
2009-06-25 10:49 ` Amerigo Wang
2009-06-25 10:49 ` Amerigo Wang
2009-06-25 14:51 ` Jeff Dike
2009-06-25 14:51 ` Jeff Dike
2009-06-26 2:01 ` Stephen Rothwell
2009-06-26 2:48 ` Jeff Dike
2009-06-26 2:48 ` Jeff Dike
2009-06-26 4:15 ` Stephen Rothwell
2009-06-26 4:15 ` Stephen Rothwell
2009-06-25 3:59 ` Stephen Rothwell
2009-06-25 7:57 ` Boaz Harrosh
2009-06-25 8:06 ` Paul Menage
2009-06-25 8:08 ` Boaz Harrosh
2009-06-25 8:08 ` Boaz Harrosh
2009-06-25 10:52 ` Amerigo Wang
2009-06-26 1:08 ` Stephen Rothwell
2009-06-26 1:07 ` 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=4A3F73A0.1010005@panasas.com \
--to=bharrosh@panasas.com \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=sfr@canb.auug.org.au \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=xiyou.wangcong@gmail.com \
/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.