I realize that now... insufficient caffeine level!
The really interesting thing is seeing how the compiler builds:
printk("fluff %s %s %s\n", in_ntoa(1), in_ntoa(2), in_ntoa(3));
That will print:
fluff 1.0.0.0 1.0.0.0 1.0.0.0 (well, maybe I have byte ordering wrong)
The calls to in_ntoa occur "backwards" and all return the same address thanks
to the "static char buffer[16]." This routine smells of a hideous #define
macro (I've done that before) or exploit gcc and create some vars in the
middle of a function. (Or compile the kernel with g++ <grin>)
--Ricky
Gee, look at the trouble I go through to avoid hex IP addresses!