From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
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 v4 6/6] staging: ramster: add how-to for ramster
Date: Sat, 13 Apr 2013 06:28:54 -0700 [thread overview]
Message-ID: <20130413132854.GA28650@kroah.com> (raw)
In-Reply-To: <1365858092-21920-7-git-send-email-liwanp@linux.vnet.ibm.com>
On Sat, Apr 13, 2013 at 09:01:32PM +0800, Wanpeng Li wrote:
> Add how-to for ramster.
>
> Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
> Singed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
> Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
> ---
> drivers/staging/zcache/ramster/HOWTO.txt | 257 ++++++++++++++++++++++++++++++
> 1 file changed, 257 insertions(+)
> create mode 100644 drivers/staging/zcache/ramster/HOWTO.txt
>
> diff --git a/drivers/staging/zcache/ramster/HOWTO.txt b/drivers/staging/zcache/ramster/HOWTO.txt
> new file mode 100644
> index 0000000..a4ee979
> --- /dev/null
> +++ b/drivers/staging/zcache/ramster/HOWTO.txt
> @@ -0,0 +1,257 @@
> +Version: 130309
> + Dan Magenheimer <dan.magenheimer@oracle.com>
If Dan wrote this, why are you listing yourself as the author of this
patch?
> +CHANGELOG:
> +v5-120214->120817: updated for merge into new zcache codebase
> +v4-120126->v5-120214: updated for V5
> +111227->v4-120126: added info on selfshrinking and rebooting
> +111227->v4-120126: added more info for tracking RAMster stats
> +111227->v4-120126: CONFIG_PREEMPT_NONE no longer necessary
> +111227->v4-120126: cleancache now works completely so no need to disable it
That is not needed in an in-kernel file, please remove it.
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 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 13:01 [PATCH PART3 v4 0/6] staging: zcache/ramster: fix and ramster/debugfs improvement Wanpeng Li
2013-04-13 13:01 ` [PATCH PART3 v4 1/6] staging: ramster: Move debugfs code out of ramster.c file Wanpeng Li
2013-04-13 13:01 ` [PATCH PART3 v4 2/6] staging: ramster/debug: Use an array to initialize/use debugfs attributes Wanpeng Li
2013-04-13 13:01 ` [PATCH PART3 v4 3/6] staging: ramster: Add incremental accessory counters Wanpeng Li
2013-04-13 13:01 ` [PATCH PART3 v4 4/6] staging: ramster/debug: Add CONFIG_RAMSTER_DEBUG Kconfig entry Wanpeng Li
2013-04-13 13:01 ` [PATCH PART3 v4 5/6] staging: zcache/debug: fix coding style Wanpeng Li
2013-04-13 13:01 ` [PATCH PART2 v4 6/6] staging: ramster: add how-to for ramster Wanpeng Li
2013-04-13 13:28 ` Greg Kroah-Hartman [this message]
2013-04-15 0:00 ` Wanpeng Li
2013-04-15 0:00 ` 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=20130413132854.GA28650@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox