Re: Section msimatch warnings

From: David Miller
Date: Mon Oct 25 2010 - 19:27:08 EST

Next message: Jeremy Fitzhardinge: "Re: [PATCH 1/5] Add a global synchronization point for pvclock"
Previous message: Herbert Xu: "Re: [PATCH] drivers/crypto: dubious error check"
In reply to: Stephen Rothwell: "Section msimatch warnings (Was: Re: linux-next: build failure aftermerge of the final tree (net-current tree related))"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Tue, 26 Oct 2010 10:04:27 +1100

> This is actually different - it is generated by the compiler. I am not
> sure why we only get them on PowerPC.

I think it has to do with how function descriptors work on powerpc.

Code references to static (local) things work different from how
global scope references work.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Jeremy Fitzhardinge: "Re: [PATCH 1/5] Add a global synchronization point for pvclock"
Previous message: Herbert Xu: "Re: [PATCH] drivers/crypto: dubious error check"
In reply to: Stephen Rothwell: "Section msimatch warnings (Was: Re: linux-next: build failure aftermerge of the final tree (net-current tree related))"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]