From: Ed Tomlinson <edt@aei.ca>
To: Pekka Enberg <penberg@cs.helsinki.fi>, Nitin Gupta <ngupta@vflare.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Hugh Dickins" <hugh.dickins@tiscali.co.uk>,
"Ed Tomlinson" <edt@aei.ca>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mm-cc@laptop.org, "Ingo Molnar" <mingo@elte.hu>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: [PATCH 2/4] virtual block device driver (ramzswap)
Date: Tue, 15 Sep 2009 07:45:14 -0400 [thread overview]
Message-ID: <200909150745.16265.edt@aei.ca> (raw)
In-Reply-To: <84144f020909150030h1f9d8062sc39057b55a7ba6c0@mail.gmail.com>
On Tuesday 15 September 2009 03:30:23 you wrote:
> > So, its extremely difficult to wait for the proper fix.
>
> Then make ramzswap depend on !CONFIG_ARM. In any case, CONFIG_ARM bits
> really don't belong into drivers/block.
Problem is that ramzswap is usefull on boxes like the n800/n810... So this is a bad
suggestion from my POV. How about a comment saying this code goes when the
fix arrives???
Ed Tomlinson
WARNING: multiple messages have this Message-ID (diff)
From: Ed Tomlinson <edt@aei.ca>
To: Pekka Enberg <penberg@cs.helsinki.fi>, Nitin Gupta <ngupta@vflare.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Hugh Dickins" <hugh.dickins@tiscali.co.uk>,
"Ed Tomlinson" <edt@aei.ca>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mm-cc@laptop.org, "Ingo Molnar" <mingo@elte.hu>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: [PATCH 2/4] virtual block device driver (ramzswap)
Date: Tue, 15 Sep 2009 07:45:14 -0400 [thread overview]
Message-ID: <200909150745.16265.edt@aei.ca> (raw)
In-Reply-To: <84144f020909150030h1f9d8062sc39057b55a7ba6c0@mail.gmail.com>
On Tuesday 15 September 2009 03:30:23 you wrote:
> > So, its extremely difficult to wait for the proper fix.
>
> Then make ramzswap depend on !CONFIG_ARM. In any case, CONFIG_ARM bits
> really don't belong into drivers/block.
Problem is that ramzswap is usefull on boxes like the n800/n810... So this is a bad
suggestion from my POV. How about a comment saying this code goes when the
fix arrives???
Ed Tomlinson
--
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-09-15 11:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909100215.36350.ngupta@vflare.org>
2009-09-09 21:19 ` [PATCH 2/4] virtual block device driver (ramzswap) Nitin Gupta
2009-09-09 21:19 ` Nitin Gupta
2009-09-14 20:10 ` Pekka Enberg
2009-09-14 20:10 ` Pekka Enberg
2009-09-15 6:39 ` Nitin Gupta
2009-09-15 6:39 ` Nitin Gupta
2009-09-15 7:30 ` Pekka Enberg
2009-09-15 7:30 ` Pekka Enberg
2009-09-15 8:21 ` Nitin Gupta
2009-09-15 8:21 ` Nitin Gupta
2009-09-15 8:30 ` Pekka Enberg
2009-09-15 8:30 ` Pekka Enberg
2009-09-15 15:26 ` Greg KH
2009-09-15 15:26 ` Greg KH
2009-09-15 15:55 ` Nitin Gupta
2009-09-15 15:55 ` Nitin Gupta
2009-09-15 11:45 ` Ed Tomlinson [this message]
2009-09-15 11:45 ` Ed Tomlinson
2009-09-15 12:42 ` Pekka Enberg
2009-09-15 12:42 ` Pekka Enberg
2009-09-15 13:14 ` Steven Rostedt
2009-09-15 13:14 ` Steven Rostedt
2009-09-15 13:43 ` Pekka Enberg
2009-09-15 13:43 ` Pekka Enberg
2009-09-15 14:08 ` Steven Rostedt
2009-09-15 14:08 ` Steven Rostedt
2009-09-09 21:21 ` [PATCH 4/4] documentation Nitin Gupta
2009-09-09 21:21 ` Nitin Gupta
2009-09-09 21:50 ` [PATCH 3/4] send callback when swap slot is freed Nitin Gupta
2009-09-09 21:50 ` Nitin Gupta
2009-09-09 21:53 ` [PATCH 1/4] xvmalloc memory allocator Nitin Gupta
2009-09-09 21:53 ` Nitin Gupta
2009-09-09 22:02 ` [PATCH 0/4] compcache: in-memory compressed swapping v2 Nitin Gupta
2009-09-09 22:02 ` Nitin Gupta
2009-09-12 2:24 ` Nitin Gupta
2009-09-12 2:24 ` Nitin Gupta
2009-09-13 19:07 ` Hugh Dickins
2009-09-13 19:07 ` Hugh Dickins
2009-09-14 4:04 ` Nitin Gupta
2009-09-14 4:04 ` Nitin Gupta
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=200909150745.16265.edt@aei.ca \
--to=edt@aei.ca \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.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.