linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kamezawa.hiroyu@jp.fujitsu.com
Subject: kcore patches (was Re: 2.6.32 -mm merge plans)
Date: Wed, 16 Sep 2009 17:35:56 +0800	[thread overview]
Message-ID: <2375c9f90909160235m1f052df0qb001f8243ed9291e@mail.gmail.com> (raw)

On Wed, Sep 16, 2009 at 7:15 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>#kcore-fix-proc-kcores-statst_size.patch: is it right?
>kcore-fix-proc-kcores-statst_size.patch

Hmm, I think KAMEZAWA Hiroyuki's patchset is a much better fix for this.
Hiroyuki?

Thanks!

--
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>

             reply	other threads:[~2009-09-16  9:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  9:35 Américo Wang [this message]
2009-09-16 11:17 ` kcore patches (was Re: 2.6.32 -mm merge plans) KAMEZAWA Hiroyuki
2009-09-17  2:41   ` [PATCH 0/3][mmotm] showing size of kcore (Was " KAMEZAWA Hiroyuki
2009-09-17  2:42     ` [PATCH 1/3][mmotm] kcore: more fixes for init KAMEZAWA Hiroyuki
2009-09-17  5:55       ` Américo Wang
2009-09-17  2:44     ` [PATCH 2/3][mmotm] showing size of kcore KAMEZAWA Hiroyuki
2009-09-17  6:02       ` Américo Wang
2009-09-17  6:10         ` [PATCH 2/3][mmotm] showing size of kcore v2 KAMEZAWA Hiroyuki
2009-09-18  2:20           ` Américo Wang
2009-09-17  2:45     ` [PATCH 3/3][mmotm] updateing size of kcore KAMEZAWA Hiroyuki
2009-09-17  6:59       ` Américo Wang
2009-09-17  7:14         ` KAMEZAWA Hiroyuki
2009-09-18  2:05           ` Américo Wang
2009-09-17  3:09   ` kcore patches (was Re: 2.6.32 -mm merge plans) Américo Wang

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=2375c9f90909160235m1f052df0qb001f8243ed9291e@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).