| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 29 Sep 2011 22:40:59 -0400 From: Paul Gortmaker <paul.gortmaker@...driver.com> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: build failure after merge of the final tree On Thu, Sep 29, 2011 at 9:12 PM, Stephen Rothwell <sfr@...b.auug.org.au> 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@...b.auug.org.au > http://www.canb.auug.org.au/~sfr/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists