From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
harvey.harrison@gmail.com, torvalds@linux-foundation.org,
davem@davemloft.net, tglx@linutronix.de, hpa@zytor.com,
xemul@openvz.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] feature-removal: add documentation for exported symbols going away
Date: Thu, 14 Feb 2008 00:18:36 +0000 [thread overview]
Message-ID: <20080214001836.687f03f7@core> (raw)
In-Reply-To: <20080213235843.GG12383@cs181133002.pp.htv.fi>
> Unexports are done immediately when there's a subsystem maintainer
> taking a patch and deprecation periods are required when a patch has to
> go through you...
Agreed - with the expect of stuff which is used in tree or forms part of
a logical exported API we should just throw them out without messing. The
only exceptions I can see that make sense are
- Where a subsystem maintainer says not to
- Where we know that a commonly used out of tree module needs it
Most of the excess symbols should thus just go away. Its pretty unlikely
that they are being used.
Alan
next prev parent reply other threads:[~2008-02-14 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 22:22 [RFC PATCH] feature-removal: add documentation for exported symbols going away Harvey Harrison
2008-02-13 22:34 ` Adrian Bunk
2008-02-13 22:42 ` Harvey Harrison
2008-02-13 22:55 ` Adrian Bunk
2008-02-13 22:43 ` Adrian Bunk
2008-02-13 22:54 ` Andrew Morton
2008-02-13 23:22 ` Adrian Bunk
2008-02-13 23:43 ` Andrew Morton
2008-02-13 23:58 ` Adrian Bunk
2008-02-14 0:18 ` Alan Cox [this message]
2008-02-13 23:07 ` Arjan van de Ven
2008-02-15 3:06 ` Rene Herman
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=20080214001836.687f03f7@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=xemul@openvz.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