LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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 01:58:43 +0200	[thread overview]
Message-ID: <20080213235843.GG12383@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080213154331.f11efc63.akpm@linux-foundation.org>

On Wed, Feb 13, 2008 at 03:43:31PM -0800, Andrew Morton wrote:
> On Thu, 14 Feb 2008 01:22:48 +0200
> Adrian Bunk <bunk@kernel.org> wrote:
> 
> > I don't get your point why bigger API changes should still be allowed 
> > without any advance warning while removing an export should require 
> > deprecation periods.
> 
> Because the cost to us of giving people a few months warning is miniscule,
> and doing so a) is courteous to our users and b) possibly avoids driving
> away testers.

The miniscule cost is my spare time and my nerves.

These unexport discussions are _the_ thing that have turned kernel 
development from having been fun into creating anger for me. If your 
goal is to bring me to quitting kernel development and spending my spare 
time differently you've already gotten quite near to reaching your goal.

> otoh the cost to us of avoiding large API changes is much much higher, so
> the tradeoff has a different outcome.
> 
> > If you want to offer a stable API for external modules then please do 
> > it completely and with all consequences.
> 
> Sorry, but you have this belief that if we do X in one case then we should
> rigorously do X in all cases.  That everything we do sets precedents which
> must be forever and in all cases followed.  That it is all about rules and
> sticking to them.  That if you can catch person A taking action B then you
> can trap that person into doing B in all cases for ever more.
> 
> Well it doesn't work like that.  Each case is different and each case has
> pros and cons and each one needs to be weighed according to those pros and
> cons.

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...

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


  reply	other threads:[~2008-02-13 23:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 22:22 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 [this message]
2008-02-14  0:18             ` Alan Cox
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=20080213235843.GG12383@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.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 \
    --subject='Re: [RFC PATCH] feature-removal: add documentation for exported symbols going away' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).