From: Chris Wright <chrisw@osdl.org>
To: zach@vmware.com
Cc: akpm@osdl.org, chrisl@vmware.com, chrisw@osdl.org, hpa@zytor.com,
jdike@addtoit.com, linux-kernel@vger.kernel.org,
mbligh@mbligh.org, pratap@vmware.com,
virtualization@lists.osdl.org, zwane@arm.linux.org.uk
Subject: Re: [PATCH 1/6] i386 virtualization - Fix uml build
Date: Mon, 15 Aug 2005 21:37:02 -0700 [thread overview]
Message-ID: <20050816043702.GS7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200508152258.j7FMwdAb005304@zach-dev.vmware.com>
* zach@vmware.com (zach@vmware.com) wrote:
> Attempt to fix the UML build by assuming the default i386 subarchitecture
> (mach-default).
>
> I can't fully test this because spinlock breakage is still happening in
> my tree, but it gets rid of the mach_xxx.h missing file warnings.
I assume this is intended to fix a build error caused by patches in the
earlier set which added more reliance on mach-default?
thanks,
-chris
next prev parent reply other threads:[~2005-08-16 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 22:58 [PATCH 1/6] i386 virtualization - Fix uml build zach
2005-08-16 4:37 ` Chris Wright [this message]
2005-08-16 5:03 ` Zachary Amsden
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=20050816043702.GS7762@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=chrisl@vmware.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pratap@vmware.com \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
--cc=zwane@arm.linux.org.uk \
/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