From: Andrew Morton <akpm@osdl.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] kernel/sys.c: possible cleanups
Date: Mon, 1 May 2006 00:49:25 -0700 [thread overview]
Message-ID: <20060501004925.36e4dd21.akpm@osdl.org> (raw)
In-Reply-To: <1146469146.20760.31.camel@laptopd505.fenrus.org>
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");
next prev parent reply other threads:[~2006-05-01 7:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 7:11 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 [this message]
2006-05-01 8:00 ` Arjan van de Ven
2006-05-01 8:20 ` Andrew Morton
2006-05-01 8:59 ` Adrian Bunk
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=20060501004925.36e4dd21.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--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
Powered by JetHome