On Fri, 2013-05-10 at 17:26 -0700, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxx> > > This is a no-op for the modular use case of the > backports project but by enabling this it allows > for developers a way to embed the backports releases > onto a target source Linux directory, with obvious > pending modifications, by adding our backport_init() > onto the target kernel's init/main.c start_kernel(). > > Enable this theoretical use case. Hackers welcome to > go play on this theoretical integration strategy now. I applied all but this one, it caused a compiler warning that seemed important (missing an include?) /tmp/i/compat/main.c:83:1: warning: data definition has no type or storage class [enabled by default] /tmp/i/compat/main.c:83:1: warning: type defaults to ‘int’ in declaration of ‘__exitcall’ [-Wimplicit-int] /tmp/i/compat/main.c:83:1: warning: parameter names (without types) in function declaration [enabled by default] /tmp/i/compat/main.c:76:123: warning: ‘backport_exit’ defined but not used [-Wunused-function] johannes -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
