All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] kernel/sys.c: remove unused exports
Date: Thu, 29 Jun 2006 23:18:08 +0200	[thread overview]
Message-ID: <20060629211807.GH19712@stusta.de> (raw)
In-Reply-To: <20060629130633.3da327b6.akpm@osdl.org>

On Thu, Jun 29, 2006 at 01:06:33PM -0700, Andrew Morton wrote:
> On Thu, 29 Jun 2006 21:58:28 +0200
> Adrian Bunk <bunk@stusta.de> wrote:
> 
> > On Thu, Jun 29, 2006 at 12:44:00PM -0700, Andrew Morton wrote:
> > > On Thu, 29 Jun 2006 12:36:08 -0700
> > > Andrew Morton <akpm@osdl.org> wrote:
> > > 
> > > > On Thu, 29 Jun 2006 21:19:40 +0200
> > > > Adrian Bunk <bunk@stusta.de> wrote:
> > > > 
> > > > > This patch removes the following unused exports:
> > > > > - EXPORT_SYMBOL:
> > > > >   - in_egroup_p
> > > > > - EXPORT_SYMBOL_GPL's:
> > > > >   - kernel_restart
> > > > >   - kernel_halt
> > > > 
> > > > Switch 'em to EXPORT_UNUSED_SYMBOL and I'll stop dropping your patches ;)
> > > > 
> > > 
> > > If doing this, I'd suggest it be done thusly:
> > > 
> > > EXPORT_UNUSED_SYMBOL(in_egroup_p);	/* June 2006 */
> > > 
> > > to aid later decision-making.
> > 
> > I had some bad experiences with following processes you suggest the 
> > doesn't remove the symbol immediately:
> > 
> > As you wanted me to do, I scheduled the EXPORT_SYMBOL(insert_resource) 
> > for removal on 2 May 2005 with both __deprecated_for_modules and an 
> > entry in feature-removal-schedule.txt with the target date April 2006.
> > 
> > On 11 Apr 2006, I sent the patch to implement this scheduled removal.
> > 
> > As of today, the latter patch is still stuck in -mm (which isn't better 
> > than having it dropped) although it's long overdue.
> 
> Blame Greg ;)

Why?

> > Do you understand why I distrust your "to aid later decision-making"?
> 
> You'll cope.
> 
> > Can you state publically "If there's still no in-kernel user after six 
> > months, the removal is automatically ACK'ed."?
> 
> 6 or 12.  We haven't decided.  6 sounds OK.  If nobody complains.  If
> they do, we rethink a particular export.

OK, I hope I'll have more luck with this process.

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:[~2006-06-29 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 19:19 [RFC: 2.6 patch] kernel/sys.c: remove unused exports Adrian Bunk
2006-06-29 19:36 ` Andrew Morton
2006-06-29 19:44   ` Andrew Morton
2006-06-29 19:58     ` Adrian Bunk
2006-06-29 20:06       ` Andrew Morton
2006-06-29 21:18         ` Adrian Bunk [this message]
2006-07-02 16:52           ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23 10:55 Adrian Bunk
2006-05-16 17:44 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=20060629211807.GH19712@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.