From: Dave Hansen <haveblue@us.ibm.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] mm/: small cleanups
Date: Mon, 07 Nov 2005 22:27:27 +0100 [thread overview]
Message-ID: <1131398847.7967.17.camel@localhost> (raw)
In-Reply-To: <20051107211836.GX3847@stusta.de>
On Mon, 2005-11-07 at 22:18 +0100, Adrian Bunk wrote:
> On Sun, Oct 30, 2005 at 03:42:32PM +0100, Dave Hansen wrote:
> > On Sun, 2005-10-30 at 02:05 +0100, Adrian Bunk wrote:
> > > This patch contains the following cleanups:
> > > - make some needlessly global functions static
> > > - vmscan.c: #if 0 the unused global function sys_set_zone_reclaim
> >
> > If it's truly unused, why not simply kill it completely?
>
> Updated patch below.
Looks better now. The net removal of 27 lines makes it much easier to
sell as a cleanup. :)
-- Dave
prev parent reply other threads:[~2005-11-07 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 1:05 [2.6 patch] mm/: small cleanups Adrian Bunk
2005-10-30 14:42 ` Dave Hansen
2005-11-07 21:18 ` Adrian Bunk
2005-11-07 21:27 ` Dave Hansen [this message]
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=1131398847.7967.17.camel@localhost \
--to=haveblue@us.ibm.com \
--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