All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	"H. Peter Anvin" <hpa@zytor.com>, stable <stable@kernel.org>
Subject: Re: [PATCH] kmemleak: Add support for NO_BOOTMEM configurations
Date: Fri, 16 Jul 2010 11:43:07 -0700	[thread overview]
Message-ID: <4C40A83B.2090108@kernel.org> (raw)
In-Reply-To: <1279269963.24890.8.camel@e102109-lin.cambridge.arm.com>

On 07/16/2010 01:46 AM, Catalin Marinas wrote:
> 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@arm.com>
>>> Cc: Pekka Enberg <penberg@cs.helsinki.fi>
>>> Cc: Yinghai Lu <yinghai@kernel.org>
>>> Cc: H. Peter Anvin <hpa@zytor.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@kernel.org when pushing the patch to Linus.
> 
> Should I consider your reply as an acked-by?
> 

Yes.

Thanks

Yinghai

  reply	other threads:[~2010-07-16 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 14:58 [PATCH] kmemleak: Add support for NO_BOOTMEM configurations Catalin Marinas
2010-07-15 17:16 ` Yinghai Lu
2010-07-16  8:46   ` Catalin Marinas
2010-07-16 18:43     ` Yinghai Lu [this message]
2010-07-16  9:01 ` Pekka Enberg

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=4C40A83B.2090108@kernel.org \
    --to=yinghai@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=stable@kernel.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.