On Mon, Dec 13, 2010 at 02:45:55PM +1100, Stephen Rothwell wrote: > Hi Nick, > > On Mon, 13 Dec 2010 13:59:10 +1100 Nick Piggin <npiggin@xxxxxxxxx> wrote: > > > > On Sun, Dec 12, 2010 at 09:53:32PM -0500, Ed Tomlinson wrote: > > > > > > I get this when building: > > > > > > security/security.c: In function 'security_inode_exec_permission': > > > security/security.c:520: error: 'rcu' undeclared (first use in this function) > > > security/security.c:520: error: (Each undeclared identifier is reported only once > > > security/security.c:520: error: for each function it appears in.) > > > make[1]: *** [security/security.o] Error 1 > > > make: *** [security] Error 2 > > > > > > Missing include maybe? > > > > Ah, missed permutation while doing a final build check. `rcu` should > > just be renamed to `flags`. > > You will, of course never put anything not build tested into a tree for > linux-next inclusion, right? ;-) Right. It will be guaranteed to have been build tested with at least one .config :) Which reminds me, I haven't done an allmodconfig recently to see if I've missed exports... -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
