LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Pavel Emelyanov <xemul@openvz.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] feature-removal: add documentation for exported symbols going away
Date: Thu, 14 Feb 2008 00:55:43 +0200	[thread overview]
Message-ID: <20080213225543.GE12383@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <1202942550.18204.18.camel@brick>

On Wed, Feb 13, 2008 at 02:42:30PM -0800, Harvey Harrison wrote:
> On Thu, 2008-02-14 at 00:34 +0200, Adrian Bunk wrote:
> > On Wed, Feb 13, 2008 at 02:22:06PM -0800, Harvey Harrison wrote:
> > > +
> > > +What:	__inet_hash_connect
> > > +Where:	net/ipv4/inet_hashtables.c
> > > +When:	2.6.28
> > > +Why:	No in tree users
> > > +
> > > +---------------------------
> > > +
> > > +What:	io_delay_type
> > > +Where:	arch/x86/kernel/io_delay.c
> > > +When:	2.6.28
> > > +Why:	No in tree users
> > > +
> > > +---------------------------
> > >...
> > 
> > NAK.
> > 
> > It's a well-known and documented fact that we not have a stable API for 
> > modules.
> > 
> > And as long as we anyway break the modules API in so many other cases 
> > with each kernel release there's simply no point in not removing exports 
> > immediately.
> > 
> > Oh, and for increasing the amount of nonsense even further, you should 
> > explain why unused exports that just sneaked into 2.6.25-rc1 must be 
> > shipped in 4 stable kernels before they can be removed.
> 
> Without comment on the validity of the exports themselves, I was more
> interested in the principle of announcing these removals, and if it
> was wanted.

Sorry again for being too harsh (see my other email).

Every kernel release has a big amount of API changes that have not been 
announced previously, and that's a fact that is rooted in the kernel
development model.

Otherwise everyone also had to announce now if he wanted to e.g. change 
a function prototype or a struct in 2.6.28.

> Cheers,
> 
> Harvey

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 22:56 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 [this message]
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
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=20080213225543.GE12383@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).