We have replaced all static inline with extern inline to keep
the size of the image down when compiling with GCC 3.2
(because the maximum size to inline has changed in 3.2 I think,
I can get a clarification from the gcc-cris guy if necessary).
Is this a non preferred way to do it?
>a junk file in arch/cris/drivers/bluetooth/bt.patch
Why is it junk? The bluetooth options should only be visible
if you have an OpenBT source tree available. The Makefile
in arch/cris/drivers/bluetooth/ checks your tree and then
runs the patch. This was previously done with a perl
script instead. In the long run we should probably switch
to the official Bluetooth stack in Linux (i.e. Bluez).
>although if Axis would glance over and fixup the ide bits
>that would be great as its not a platform I have access too
Yes, I will take a look at it
/Mikael
-
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/