Re: [patch] uninline remove/add_parent() APIs

I'm travelling this week (through Monday) and can't be of much immediate help on improving the situation or explaining it in great detail. Last week before I left home I was deep in some strange debugging and didn't get a chance to look up. There will be more of that, but I'll try to make some ti

Re: [patch] uninline remove/add_parent() APIs

Andrew Morton <[EMAIL PROTECTED]> writes: > On Wed, 11 Apr 2007 01:00:17 -0600 > [EMAIL PROTECTED] (Eric W. Biederman) wrote: > >> Should we copy Andrew or is someone else going to collect up all of these > patches? > > Andrew is cowering in terror, because utrace goes tromping through this > code

Re: [patch] uninline remove/add_parent() APIs

On Wed, 11 Apr 2007 01:00:17 -0600 [EMAIL PROTECTED] (Eric W. Biederman) wrote: > Should we copy Andrew or is someone else going to collect up all of these > patches? Andrew is cowering in terror, because utrace goes tromping through this code. It would be rather good to get utrace moving along

Re: [patch] uninline remove/add_parent() APIs

Ingo Molnar <[EMAIL PROTECTED]> writes: > here's a (tested) patch i did that should simplify changes done to > p->children and p->sibling handling. Looks reasonable. Acked-by: "Eric W. Biederman" <[EMAIL PROTECTED]> Should we copy Andrew or is someone else going to collect up all of these pat

[patch] uninline remove/add_parent() APIs

here's a (tested) patch i did that should simplify changes done to p->children and p->sibling handling. Ingo --> Subject: [patch] uninline remove/add_parent() APIs From: Ingo Molnar <[EMAIL PROTECTED]> uninline/simplify remove/add_parent()