Hi Konstantin,
On Mon, Oct 08, 2007 at 03:34:24PM +0300, Konstantin Oshovskij wrote:
The "may be used uninitialized" errors are false positives from GCC. Mostly
this happens from code paths like:
int x, y;
set_method(&x);
y = x;
Hidden by uninitialized_var() macro in latest pull. This macro silence
the gcc by using the trick: #define uninitialized_var(x) x = x
Already hidden now by the uninitialized_var() macro.
pci_find_slot is using pci_find_device on purpose here (equivalent to the
safe pci_get_slot method).
False positives from function definition and from the innocent EXPORT_SYMBOL
macro (It makes the method available to kernel modules).
Regards,
--
Ahmed S. Darwish
HomePage: http://darwish.07.googlepages.com
Blog: http://darwish-07.blogspot.com
-