From: Catalin Marinas <catalin.marinas@arm.com>
To: Wang YanQing <udknight@gmail.com>,
rob@landley.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update kmemleak.txt
Date: Wed, 19 Feb 2014 10:04:16 +0000 [thread overview]
Message-ID: <20140219100415.GB30457@arm.com> (raw)
In-Reply-To: <20140216164205.GA5941@udknight>
On Sun, Feb 16, 2014 at 04:42:05PM +0000, Wang YanQing wrote:
> Update Documentatin/kmemleak.txt to
> reflect the following changes:
>
> Commit b69ec42b1b194cc88f04b3fbcda8d3f93182d6c3
> ("Kconfig: clean up the long arch list for the DEBUG_KMEMLEAK config option")
> make we can't check supported architectures by read Kconfig.debug.
>
> Commit 85d3a316c714197f94e75c1e5b2d37607d66e5de
> ("kmemleak: use rbtree instead of prio tree")
> convert kmemleak to use rbtree instead of prio tree.
>
> Signed-off-by: Wang YanQing <udknight@gmail.com>
Since it looks like akpm is picking this patch:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Thanks.
prev parent reply other threads:[~2014-02-19 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 16:42 [PATCH] Documentation: update kmemleak.txt Wang YanQing
2014-02-19 10:04 ` Catalin Marinas [this message]
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=20140219100415.GB30457@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=udknight@gmail.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