Without CONFIG_DEBUG_SPINLOCK configured in I'm getting a large number
of "implicit declaration of function ‘__raw_read_unlock’" warnings and a
subsequent failure at the link stage.
A trivial change to include/linux/spinlock_up.h (i.e. moving the
definition of __raw_read_unlock() outside the ifdef) can get rid of this
warning but I'm not sure that it's the right thing to do as I suspect
this may be an indication of a less trivial problem elsewhere.
Peter
--
Peter Williams [email protected]
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
