On Thu, Jun 28, 2007 at 03:39:49PM -0700, Andrew Morton wrote:No, it's correct. It simply says that this code can only be discarted after initialization if it's not a module, since it's also used from __exit code. The idea behind __init_or_module is that __exit code is never executed for non-modular code, and such cases where some function is executed both by both __init and __exit and never from other code aren't that unusual. I'm not sure how realistic it is, but it would be best if we could at some point in the future simply give gcc a few basic hints that stuff like module_init() can use code that is __init and let gcc figure out which code to move to this section... cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -
| Trent Piepho | [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
| Stoyan Gaydarov | From 2.4 to 2.6 to 2.7? |
| Andi Kleen | [PATCH] [4/50] x86: add cpu codenames for Kconfig.cpu |
| Greg Kroah-Hartman | [PATCH 013/196] Documentation: Replace obsolete "driverfs" with "sysfs". |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: HTB accuracy for high speed |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
