On Fri, 27 Jun 2008 14:43:20 -0700
Roland Dreier <rdreier@cisco.com> wrote:
That's the general idea: audit the code where the BKL appears and
remove it when it's safe to do so. It's always an appropriate time;
the only question is whether you think this change is good to go into
the tree for 2.6.27, or whether it should hang out in linux-next for
one more cycle. I would assume that the extra time would not be
necessary.
Thanks,
jon
--