From: Amerigo Wang <xiyou.wangcong@gmail.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 16:57:35 +0800 [thread overview]
Message-ID: <20090622085735.GB6499@cr0.nay.redhat.com> (raw)
In-Reply-To: <4A3F4448.30502@panasas.com>
On Mon, Jun 22, 2009 at 11:43:52AM +0300, Boaz Harrosh wrote:
>
>Stephan hi.
>
>The above breakage is the usual stuff we get every merge window. With people doing
>cross arch work and neglecting UML.
>
>Who is the person or people responsible for the large linux-next compilation rig?
>Is it possible to also add a UML traget, at least for the x86_64/x86_32 sub-arch?
Agreed.
Stephan, could you please also do compiling tests for UML in your -next tree?
Thanks!
next prev parent reply other threads:[~2009-06-22 8:57 UTC|newest]
Thread overview: 20+ 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 [this message]
2009-06-22 10:52 ` Stephen Rothwell
2009-06-22 12:05 ` Boaz Harrosh
2009-06-25 10:49 ` Amerigo Wang
2009-06-25 14:51 ` Jeff Dike
2009-06-26 2:01 ` Stephen Rothwell
2009-06-26 2:48 ` Jeff Dike
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 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=20090622085735.GB6499@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--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 \
/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