On Thu, Sep 29, 2011 at 9:12 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi all, > > After merging the final tree, today's linux-next build (avr32 allnoconfig) > failed like this: > > arch/avr32/mach-at32ap/pio.c: In function 'pio_probe': > arch/avr32/mach-at32ap/pio.c:401: error: 'THIS_MODULE' undeclared (first use in this function) > > Probably revealed by the module.h split up. I guess it needs export.h > included. Since export.h does not exist for most people, I'm OK adding it in instances like this as a post-merge patch. For instances where it is obvious that the full module.h is required, I'd rather the originator of the new module dependent code simply add the required module.h themselves. (I think this is consistent with what Stephen has been recommending to people on a case-by-case basis anyway). I can/will temporarily add the module.h cases to the post-merge queue too, but my intention is to move as many of these post-merge commits off to the sub-maintainers as possible. P. > -- > Cheers, > Stephen Rothwell sfr@xxxxxxxxxxxxxxxx > http://www.canb.auug.org.au/~sfr/ > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
