> I've toyed with this idea, but wondered if perhaps a seperate
> document would be a better idea. Ie, keep this one as a
> end-users guide, and have a seperate programmers guide
> covering things like API changes and the likes.
> The latter would likely be more time consuming than the former,
> we'll see how things go..
Good idea :)
> Wasn't there also some issue in various drivers ? I believe Alan cited
> the 8390 net driver as one example.
Yes, its mainly a performance problem. In the 8390, for example, you
can get preempted with the specific interrupt disabled (from
disable_irq()).
I will get to fixing those... but biggest concern is the remaining
unprotected per-CPU data. Which, thankfully, is looking really good -
we are stable.
> > Albert's tree is a fork.
>
> *sigh* politics. I changed that text after Albert mailed me complaining
> about the original. Something tells me I'm not going to be able to
> please both of you. I'll mangle it again, and see which one of you
> complains next time 8-)
Sigh, I guess. The politics should be whose tree is better - there
should be no issue that Michael Johnson's tree is the original.
> All other suggestions added/changed/etc.
>
> Thanks for the feedback
You are welcome.
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/