From: Adrian Bunk <bunk@stusta.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] what's the value of "__deprecated_for_modules"?
Date: Wed, 17 Jan 2007 16:56:49 +0000 [thread overview]
Message-ID: <20070117165649.GJ3465@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0701171108490.1461@CPE00045a9c397f-CM001225dbafb6>
On Wed, Jan 17, 2007 at 11:11:46AM -0500, Robert P. J. Day wrote:
>
> is there really an overwhelming rationale for the following?
>
> include/linux/compiler.h:
> -------------------------
> ...
> #ifdef MODULE
> #define __deprecated_for_modules __deprecated
> #else
> #define __deprecated_for_modules
> #endif
> ...
This translates to "this EXPORT_SYMBOL will soon cvanish".
> when there's only one usage of that macro in the entire tree?
>
> include/linux/pagemap.h:
> extern __deprecated_for_modules struct page * find_trylock_page(
>
> it just seems odd that a "useful" macro would have only one
> application throughout the entire kernel.
This depends on the tree you are looking at. ;-)
E.g. in 2.6.19 include/linux/crypto.h contained half a dozen additional
ones.
One point about deprecated code it that it will be removed - which can
make the number of concurrent users quite low.
> rday
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
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-01-17 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 16:11 [KJ] what's the value of "__deprecated_for_modules"? Robert P. J. Day
2007-01-17 16:56 ` Adrian Bunk [this message]
2007-01-17 17:06 ` Robert P. J. Day
2007-01-17 18:26 ` Nishanth Aravamudan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070117165649.GJ3465@stusta.de \
--to=bunk@stusta.de \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.