linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Al Viro <viro@ftp.linux.org.uk>, Jeff Dike <jdike@addtoit.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [uml-devel] Re: UML/2.6.14-rc3 doesn't work fixes
Date: Mon, 3 Oct 2005 20:56:18 +0200	[thread overview]
Message-ID: <200510032056.18439.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20051002183758.GR7992@ftp.linux.org.uk>

On Sunday 02 October 2005 20:37, Al Viro wrote:
> On Sun, Oct 02, 2005 at 08:01:21PM +0200, Blaisorblade wrote:
> > On Sunday 02 October 2005 17:51, Jeff Dike wrote:

> > Al, is that ok for you if we follow this original plan?
> >
> > In this case, I'll post the dropping patch and re-send the Kbuild fix of
> > my last batch (conflicted with Al's patch, but now it's needed again).

> Up to Jeff; IMO it's easier to restore the variant past his review (with
> incremental replacing that DEFINE_LONGS), but maintainer gets to decide;
> that was the reason for Cc when patch got sent to Linus, after all...

My only worry is that some other bug may have slipped through - it's not the 
case that we are perfect, nor we have a real test-suite to catch this sort of 
thing (especially, there are sections of FPU handling which are buggy anyway 
- there is a really big patch which copies whole sections of i386 low level 
messing up with FPU, which I requested Jeff to hold some time ago).
-- 
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

		
___________________________________ 
Yahoo! Messenger: chiamate gratuite in tutto il mondo 
http://it.messenger.yahoo.com



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2005-10-03 18:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02 10:13 [uml-devel] UML/2.6.14-rc3 doesn't work fixes Blaisorblade
2005-10-02 11:38 ` [uml-devel] " Al Viro
2005-10-02 11:50   ` Blaisorblade
2005-10-02 17:32     ` Al Viro
2005-10-02 17:45       ` Blaisorblade
2005-10-02 15:51 ` Jeff Dike
2005-10-02 16:55   ` Al Viro
2005-10-02 18:01   ` Blaisorblade
2005-10-02 18:37     ` Al Viro
2005-10-02 20:54       ` Al Viro
2005-10-03 18:30         ` Blaisorblade
2005-10-03 23:38           ` Al Viro
2005-10-04 10:26             ` Blaisorblade
2005-10-04 11:09               ` Al Viro
2005-10-04 11:19                 ` Blaisorblade
2005-10-04 11:55                   ` Al Viro
2005-10-04 12:09                     ` Blaisorblade
2005-10-04 17:09           ` Al Viro
2005-10-04 17:14             ` Al Viro
2005-10-04 17:18               ` Al Viro
2005-10-04 17:24                 ` Al Viro
2005-10-04 17:28                   ` Al Viro
2005-10-09 19:16                   ` Blaisorblade
2005-10-03 18:56       ` Blaisorblade [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=200510032056.18439.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=viro@ftp.linux.org.uk \
    --cc=viro@zeniv.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