From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: akpm@osdl.org, Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 2/8] UML - Define jmpbuf access constants
Date: Sun, 4 Jun 2006 20:19:59 +0200 [thread overview]
Message-ID: <200606042020.00120.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060208164301.GC5240@ccure.user-mode-linux.org>
On Wednesday 08 February 2006 17:43, Jeff Dike wrote:
> On Tue, Feb 07, 2006 at 11:23:42AM -0800, Ulrich Drepper wrote:
> > If you need this
> > functionality, implement it yourself. setjmp is most likely overkill
> > anyway.
>
> OK, I'll roll my own version.
What about #ifdef'ing out the offending code #ifndef one of these constants
(they'll be defined or not altogether). As expectable, this wasn't yet
implemented - let's give the right priority to things.
(I've just met this on my SuSE, btw, which prompted me to write this email).
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-06-06 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 2:23 [uml-devel] [PATCH 2/8] UML - Define jmpbuf access constants Jeff Dike
2006-02-07 17:37 ` [uml-devel] " Ulrich Drepper
2006-02-07 18:57 ` Jeff Dike
2006-02-07 19:23 ` Ulrich Drepper
2006-02-08 16:43 ` Jeff Dike
2006-06-04 18:19 ` Blaisorblade [this message]
2006-06-05 15:40 ` [uml-devel] " Jeff Dike
2006-06-07 17:33 ` Blaisorblade
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=200606042020.00120.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--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