Very Computer

1. PATCH: Replace current->state with set_current_state in 2.5.6 8

http://muss.mcmaster.ca/~devenyga/patch-linux-2.5.68-set_current_stat...

Some time ago I sent a patch doing this only on */fs/* [not the filesystem's
code, just the common stuff]. It was dismissed by Linus under
I-don't-know-what
-the-hell-reasons (it's very smart to dismiss something without reason,
gives
the original poster a very clear idea of what needs to be changed -
nevermind,
just being ironic).

However, I'd suggest to post this into the Kernel Janitors mailing list and
let one of the big guys there swipe it in.

Maybe Robert Love can provide more highlight.

I?aky Prez-Gonzlez -- Not speaking for Intel -- all opinions are my own
(and my fault)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Are there tools to controll IPC's

3. PATCH: Replace current->state with set_current_state in 2.5.68

4. Thanks, but...

5. set_current_state(); vs current->state = bla;

6. Help. I broke my XLOCK program

7. Use __set_current_state() instead of current->state = (take 1)

8. pointer to 30char minix mkfs

9. Use __set_current_state() instead of current->state = (take 3)

10. Use __set_current_state() instead of current-> state = (take 1)

11. Use __set_current_state() instead of current->state = (take 3)

12. Use __set_current_state() instead of current->state = (take 2)

13. Cleanup of current->state for __set_current_state in linu x/fs/*.c