From: majianpeng <majianpeng@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] mm/kmemleak.c: Fix some trivial problems.
Date: Tue, 14 May 2013 19:49:27 +0800 [thread overview]
Message-ID: <519224C7.3010908@gmail.com> (raw)
Jianpeng Ma (3):
mm/kmemleak.c: Use %u to print ->checksum.
mm/kmemleak.c: Use list_for_each_entry_safe to reconstruct function
scan_gray_list.
mm/kmemleak.c: Merge the consecutive scan-areas.
mm/kmemleak.c | 36 +++++++++++++++++++++---------------
1 file changed, 21 insertions(+), 15 deletions(-)
--
1.8.3.rc1.44.gb387c77
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: majianpeng <majianpeng@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] mm/kmemleak.c: Fix some trivial problems.
Date: Tue, 14 May 2013 19:49:27 +0800 [thread overview]
Message-ID: <519224C7.3010908@gmail.com> (raw)
Jianpeng Ma (3):
mm/kmemleak.c: Use %u to print ->checksum.
mm/kmemleak.c: Use list_for_each_entry_safe to reconstruct function
scan_gray_list.
mm/kmemleak.c: Merge the consecutive scan-areas.
mm/kmemleak.c | 36 +++++++++++++++++++++---------------
1 file changed, 21 insertions(+), 15 deletions(-)
--
1.8.3.rc1.44.gb387c77
next reply other threads:[~2013-05-14 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 11:49 majianpeng [this message]
2013-05-14 11:49 ` [PATCH 0/3] mm/kmemleak.c: Fix some trivial problems majianpeng
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=519224C7.3010908@gmail.com \
--to=majianpeng@gmail.com \
--cc=catalin.marinas@arm.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 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.