The TTY layer isn't "recent code", its "very old code", and (IMO)
removing the BKL from the TTY layer is a far from trivial matter.
I believe at this point in the 2.5 cycle, we should not be looking
to remove the BKL.  We should be looking to fix the problems we know
about.  That basically means:
- module refcounting
- interrupt races
- any other races (eg, tty_register_driver / tty_unregister_driver)
-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/