[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1279269963.24890.8.camel@e102109-lin.cambridge.arm.com>
Date: Fri, 16 Jul 2010 09:46:03 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: linux-kernel@...r.kernel.org,
Pekka Enberg <penberg@...helsinki.fi>,
"H. Peter Anvin" <hpa@...or.com>, stable <stable@...nel.org>
Subject: Re: [PATCH] kmemleak: Add support for NO_BOOTMEM configurations
On Thu, 2010-07-15 at 18:16 +0100, Yinghai Lu wrote:
On 07/15/2010 07:58 AM, Catalin Marinas wrote:
> > With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
> > friends use the early_res functions for memory management when
> > NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
> > corresponding code paths for bootmem allocations.
> >
> > Signed-off-by: Catalin Marinas <catalin.marinas@....com>
> > Cc: Pekka Enberg <penberg@...helsinki.fi>
> > Cc: Yinghai Lu <yinghai@...nel.org>
> > Cc: H. Peter Anvin <hpa@...or.com>
>
> should be for 2.6.34 and 2.6.35.
I only noticed it recently since we don't have NO_BOOTMEM on ARM.
Anyway, I'll cc stable@...nel.org when pushing the patch to Linus.
Should I consider your reply as an acked-by?
Thanks.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists