public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] kernel/sys.c: possible cleanups
Date: Mon, 1 May 2006 00:38:33 -0700	[thread overview]
Message-ID: <20060501003833.340ced5b.akpm@osdl.org> (raw)
In-Reply-To: <20060501073514.GQ3570@stusta.de>

Adrian Bunk <bunk@stusta.de> wrote:
>
> On Mon, May 01, 2006 at 12:18:03AM -0700, Andrew Morton wrote:
> > Adrian Bunk <bunk@stusta.de> wrote:
> > >
> > > This patch contains the following possible cleanups:
> > 
> > Please avoid mixing together cleanups
> > 
> > >  - proper prototypes for the following functions:
> > >    - ctrl_alt_del()  (in include/linux/reboot.h)
> > >    - getrusage()     (in include/linux/resource.h)
> > >  - make the following needlessly global functions static:
> > >    - kernel_restart_prepare()
> > >    - kernel_kexec()
> > 
> > which I will apply, together with API changes
> 
> Are you splitting the patch yourself or should I send a splitted patch?

I currently have queued:

drivers/char/hw_random.c: remove assert()'s
drivers/char/applicom.c: proper module_{init,exit}
fs/buffer.c: possible cleanups
fs/open.c: unexport sys_openat

So please redo and resend the rest.

No particular hurry - I'll be out of the patch business for the next week.

> > >  - remove the following unused EXPORT_SYMBOL:
> > >    - in_egroup_p
> > >  - remove the following unused EXPORT_SYMBOL_GPL's:
> > >    - kernel_restart
> > >    - kernel_halt
> > 
> > which I will not.
> > 
> > We have a process for the latter.  And even if we ignore that process, the
> > patch ends up sitting in -mm for ages because of the API change, along with
> > the cleanups, which could be merged up promptly.
> 
> The problem is that we have a lack of a process at the other end:
> 
> There is no process to review added exports.

Yes there is - I and many others frequently query them.  Sure, sometimes
stuff slips through.  But it's a very very minor problem.


  reply	other threads:[~2006-05-01  7:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  7:11 [RFC: 2.6 patch] kernel/sys.c: possible cleanups Adrian Bunk
2006-05-01  7:18 ` Andrew Morton
2006-05-01  7:35   ` Adrian Bunk
2006-05-01  7:38     ` Andrew Morton [this message]
2006-05-01  8:13       ` Adrian Bunk
2006-05-01  7:39     ` Arjan van de Ven
2006-05-01  7:49       ` Andrew Morton
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=20060501003833.340ced5b.akpm@osdl.org \
    --to=akpm@osdl.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