compatmac is not needed

Er, compatmac is there to make new code work in older kernels. The only concession we have to make for compatibility in the actual code is that #include, and we put all the ugliness into compatmac.h which makes it work in older kernels.

So compatmac.h ends up _empty_ in the latest kernel, but that doesn't mean it's not needed.

Please don't break stuff just for the sake of it.

dwmw2

So this is still a valid API? Good to know.

What I don't know: Can it be product specific? So the net people ship a version for new networking APIs and filesystem people ship new filesystem methods along with their filesystem support.

Reason I ask: There are many such frameworks floating around, but none was complete. Many miss BUG_ON(), likely()/unlikely(), seq_file support and many more interesting stuff.

Regards

Ingo Oeser

Marketing ist die Kunst, Leuten Sachen zu verkaufen, die sie
nicht brauchen, mit Geld, was sie nicht haben, um Leute zu
beeindrucken, die sie nicht moegen.

Well, my copy of include/linux/mtd/compatmac.h includes just about everything needed to get the CVS MTD code, which is meant for 2.5, to build and work on 2.4.

There's definitely some scope for merging the various hacks if you're so inclined.

dwmw2