> If you build with preempt=N (for the scheduler stuff) the link of the
> kernel fails.
What, someone does not use preemption? 8)
An updated patch is available:
I missed the definition of the new spin_unlock_no_resched from 2.5 in
the !CONFIG_PREEMPT case. Thank you for pointing this out.
Robert Love
-
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/