> I said nothing about 2.6...
Well, 2.5 will become 2.6, and I doubt that Linus will remove the preemptible stuff at that point. > > > Well, it's either AFS or the preemption patch. You can choose... > > > > That's a bit harsh, isn't it? I'd say that the right choice is the > > third choice: fix it. Has anybody investigated this matter into more > > detail? Is Robert Love (preemptible patch maintainer) aware of the > > problem? Is the problem with OpenAFS or with the preemptible patch? > > How come a patch that does not affect any of the OpenAFS code breaks > > OpenAFS? Interesting questions I'd say... And even more because they > > will have to be answered for the > 2.4 future. > > I don't think it's harsh at all. You're welcome to submit patches to > fix it. That's exactly my point. You say it's either AFS or preemptible. I say that that's harsh, because there is a third choice: fixing it. Thank you for suggesting that I would be able to write a patch to fix this, but I doubt that I would be the right person, being totally unfamiliar with the OpenAFS code and only slightly with the preemptible code. That's why I asked those questions. Maarten _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
