From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] kernel/sys.c: possible cleanups
Date: Mon, 1 May 2006 10:59:39 +0200 [thread overview]
Message-ID: <20060501085939.GV3570@stusta.de> (raw)
In-Reply-To: <20060501004925.36e4dd21.akpm@osdl.org>
On Mon, May 01, 2006 at 12:49:25AM -0700, Andrew Morton wrote:
> Arjan van de Ven <arjan@infradead.org> wrote:
> >
> > > If removing exports requires a process, adding exports requires a
> > > similar process.
> >
> > alternatively we should bite the bullet, and just stick those 900 on the
> > "we'll kill all these in 3 months" list, have a thing to disable them
> > now via a config option (so that people actually notice rather than just
> > having them in the depreciation file) and fix the 5 or 10 or so that
> > actually will be used soon in those 3 months.
> >
>
> I'd instead suggest that we implement a new EXPORT_SYMBOL_UNEXPORT_SCHEDULED
> (?) and use that. Suitable compile-time and modprobe-time warnings would
> be needed. Put the unexport date in a comment at the
> EXPORT_SYMBOL_UNEXPORT_SCHEDULED site or even in the modprobe-time warning
> message, if that's convenient:
>
> EXPORT_SYMBOL_UNEXPORT_SCHEDULED(foo, "Dec 2006");
__deprecated_for_modules already does everything required for compile
time warnings.
No need to make the kernel image even bigger for unused stuff.
Looking over the patches I sent, this might affect perhaps 200 unused
exports today.
So the work would expand to:
- writing 200 feature-removal-schedule.txt entries
- marking 200 functions and variables as __deprecated_for_modules
And in a few months:
- removing 200 feature-removal-schedule.txt entries
- removing 200 __deprecated_for_modules markers
- removing the 200 unused exports
But what do we gain by doing this extra work?
As I said in my other email, there is no good reason to not break
external modules.
And this is reaching the point where I'm spending too much of the part
of my spare time I'm devoting to Linux kernel development in following
useless processes instead of doing something having a result making it
worth spending my time for.
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
next prev parent reply other threads:[~2006-05-01 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 7:11 [RFC: 2.6 patch] kernel/sys.c: possible cleanups Adrian Bunk
2006-05-01 7:18 ` Andrew Morton
2006-05-01 7:35 ` Adrian Bunk
2006-05-01 7:38 ` Andrew Morton
2006-05-01 8:13 ` Adrian Bunk
2006-05-01 7:39 ` Arjan van de Ven
2006-05-01 7:49 ` Andrew Morton
2006-05-01 8:00 ` Arjan van de Ven
2006-05-01 8:20 ` Andrew Morton
2006-05-01 8:59 ` Adrian Bunk [this message]
2006-05-01 9:06 ` Arjan van de Ven
2006-05-01 9:07 ` Andrew Morton
2006-05-01 9:24 ` Adrian Bunk
2006-05-16 17:43 ` [2.6 patch] kernel/sys.c: cleanups Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 17:47 [RFC: 2.6 patch] kernel/sys.c: possible cleanups Adrian Bunk
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=20060501085939.GV3570@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox