I see, if a function in a module is not marked by static ,it can be accessed by any other function in kernel, while , using a static can avoid it . thanks a lot !! 2005/8/11, Giuliano Pochini <pochini@denise.shiny.it>: > > > On Thu, 11 Aug 2005, n l wrote: > > > could you explain its reason for using static ? > > Anything which is never referenced from another file should be > static in order to keep namespace pollution low. > > > -- > Giuliano. > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: why the interrupt handler should be marked "static" for it is never called directly from another file.
- From: Zachary Amsden <zach@vmware.com>
- Re: why the interrupt handler should be marked "static" for it is never called directly from another file.
- References:
- why the interrupt handler should be marked "static" for it is never called directly from another file.
- From: n l <walking.to.remember@gmail.com>
- Re: why the interrupt handler should be marked "static" for it is never called directly from another file.
- From: Giuliano Pochini <pochini@denise.shiny.it>
- why the interrupt handler should be marked "static" for it is never called directly from another file.
- Prev by Date: Re: why the interrupt handler should be marked "static" for it is never called directly from another file.
- Next by Date: Re: How to reclaim inode pages on demand
- Previous by thread: Re: why the interrupt handler should be marked "static" for it is never called directly from another file.
- Next by thread: Re: why the interrupt handler should be marked "static" for it is never called directly from another file.
- Index(es):
