From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Garzik <jeff@garzik.org>,
jdike@karaya.com, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] UML build broken everywhere?
Date: Fri, 14 Jul 2006 16:37:44 -0400 [thread overview]
Message-ID: <20060714203744.GA6260@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200607142052.05666.blaisorblade@yahoo.it>
On Fri, Jul 14, 2006 at 08:52:05PM +0200, Blaisorblade wrote:
> Jeff (Dike), please choose one of the "simple" patches I suggested (comment
> out offending code, for instance) since you (correctly) deferred the real fix
> (incorporating klibc's setjmp implementation) to later.
Well, I have a patch which just copies the klibc setjmp stuff into the UML
tree until such time as klibc makes it into mainline.
Any objections?
Jeff
prev parent reply other threads:[~2006-07-14 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 13:23 UML build broken everywhere? Jeff Garzik
2006-07-14 13:45 ` Jeff Garzik
2006-07-14 18:52 ` [uml-devel] " Blaisorblade
2006-07-14 20:37 ` Jeff Dike [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=20060714203744.GA6260@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@karaya.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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