From: Bryan O'Sullivan <[email protected]>
Date: Tue, 11 Jul 2006 15:05:08 -0700
> Well, exactly this scheme seems to work for __iowrite_copy*. There's a
> weak generic version and a strong version in arch/x86_64/lib that
> overrides it, and it gets picked up at kernel link time.
It is linked in as an object, not into the library archive,
that's why that one works like that.
That is why io.o is added to the "obj-y" variable instead of the
"lib-y" variable. It is also necessary to link these things
in as objects when module exports are present, because if there
is no in-kernel reference to the function, you won't get the
function nor it's module export :)
-
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]
