From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Andi Kleen <andi@firstfloor.org>,
Minchan Kim <minchan.kim@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH 2/2] remove CONFIG_UNEVICTABLE_LRU definition from defconfig
Date: Thu, 28 May 2009 17:37:12 +0900 (JST) [thread overview]
Message-ID: <20090528173242.92E4.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090528013146.6dd99aa0.akpm@linux-foundation.org>
> On Thu, 14 May 2009 11:15:49 +0900 (JST) KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
> > Subject: [PATCH] remove CONFIG_UNEVICTABLE_LRU definition from defconfig
> >
> > Now, There isn't CONFIG_UNEVICTABLE_LRU. these line are unnecessary.
> >
> > ...
> >
> > 196 files changed, 196 deletions(-)
>
> Gad.
>
> I don't know if this is worth bothering about really. The dead Kconfig
> option will slowly die a natural death as people refresh the defconfig
> files.
ok. I'll drop this patch.
Sorry, I did not have the experience that changed defconfig ;)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-05-28 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 2:05 [PATCH 1/2] remove CONFIG_UNEVICTABLE_LRU config option KOSAKI Motohiro
2009-05-14 2:15 ` [PATCH 2/2] remove CONFIG_UNEVICTABLE_LRU definition from defconfig KOSAKI Motohiro
2009-05-14 2:29 ` Minchan Kim
2009-05-28 8:31 ` Andrew Morton
2009-05-28 8:37 ` KOSAKI Motohiro [this message]
2009-05-28 8:44 ` Andrew Morton
2009-05-14 2:27 ` [PATCH 1/2] remove CONFIG_UNEVICTABLE_LRU config option Minchan Kim
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=20090528173242.92E4.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dwmw2@infradead.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=mpm@selenic.com \
/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