From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Minchan Kim <minchan@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Bob Liu <bob.liu@oracle.com>
Subject: Re: [PATCH PART2 v2 2/7] staging: ramster: Move debugfs code out of ramster.c file
Date: Sat, 13 Apr 2013 08:29:39 +0800 [thread overview]
Message-ID: <20130413002939.GB17996@hacker.(null)> (raw)
In-Reply-To: <20130412221744.GA11340@kroah.com>
On Fri, Apr 12, 2013 at 03:17:44PM -0700, Greg Kroah-Hartman wrote:
>On Fri, Apr 12, 2013 at 03:16:03PM -0700, Greg Kroah-Hartman wrote:
>> On Fri, Apr 12, 2013 at 09:31:22AM +0800, Wanpeng Li wrote:
>> > Note that at this point there is no CONFIG_RAMSTER_DEBUG
>> > option in the Kconfig. So in effect all of the counters
>> > are nop until that option gets re-introduced in:
>> > zcache/ramster/debug: Add RAMSTE_DEBUG Kconfig entry
>>
>> RAMSTE_DEBUG? :)
>>
>
>And I fat-fingered my scripts, and deleted this email, sorry.
>
No problem, I will send 2-7 ASAP. ;-)
Regards,
Wanpeng Li
>Can you send the 2-7 patches again, it's my fault.
>
>greg k-h
--
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:[~2013-04-13 0:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 1:31 [PATCH PART2 v2 0/7] staging: zcache/ramster: fix and ramster/debugfs improvement Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 1/7] staging: ramster: decrease foregin pers pages when count < 0 Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 2/7] staging: ramster: Move debugfs code out of ramster.c file Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 22:16 ` Greg Kroah-Hartman
2013-04-12 22:16 ` Greg Kroah-Hartman
2013-04-12 22:17 ` Greg Kroah-Hartman
2013-04-12 22:17 ` Greg Kroah-Hartman
2013-04-13 0:29 ` Wanpeng Li
2013-04-13 0:29 ` Wanpeng Li [this message]
[not found] ` <5168a707.22e7420a.160b.ffffc573SMTPIN_ADDED_BROKEN@mx.google.com>
2013-04-13 3:05 ` Greg Kroah-Hartman
2013-04-13 3:05 ` Greg Kroah-Hartman
2013-04-13 0:28 ` Wanpeng Li
2013-04-13 0:28 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 3/7] staging: ramster/debug: Use an array to initialize/use debugfs attributes Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 4/7] staging: ramster: Add incremental accessory counters Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 5/7] staging: ramster/debug: Add RAMSTER_DEBUG Kconfig entry Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 6/7] staging: zcache/debug: fix coding style Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
2013-04-12 1:31 ` [PATCH PART2 v2 7/7] staging: ramster: add how-to for ramster Wanpeng Li
2013-04-12 1:31 ` Wanpeng Li
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='20130413002939.GB17996@hacker.(null)' \
--to=liwanp@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sjenning@linux.vnet.ibm.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 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.