mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	paulmck@linux.vnet.ibm.com, akpm@linux-foundation.org,
	mingo@elte.hu, fweisbec@gmail.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	penberg@kernel.org
Subject: Re: [PATCH] kmemleak: build kmemleak-test.c as a module-only
Date: Wed, 30 Mar 2011 08:24:19 -0700	[thread overview]
Message-ID: <20110330082419.b782fa94.rdunlap@xenotime.net> (raw)
In-Reply-To: <AANLkTim3-6vrS8uEEm+jsuSJ64z_Edq40+MqF-m2ve5=@mail.gmail.com>

On Wed, 30 Mar 2011 18:02:02 +0300 Daniel Baluta wrote:

> On Fri, Mar 25, 2011 at 4:05 PM, Daniel Baluta <dbaluta@ixiacom.com> wrote:
> > On Wed, Mar 23, 2011 at 1:24 PM, Catalin Marinas
> > <catalin.marinas@arm.com> wrote:
> >> On Wed, 2011-03-16 at 18:16 +0000, Daniel Baluta wrote:
> >>> mm/kmemleak-test.c is used to provide an example of how kmemleak
> >>> tool works.
> >>>
> >>> Memory is leaked at module unload-time, so building the test
> >>> in kernel (Y) makes the leaks impossible and the test useless.
> >>>
> >>> Qualify DEBUG_KMEMLEAK_TEST config symbol with "depends on m",
> >>> to restrict module-only building.
> >>>
> >>> Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
> >>
> >> Sorry for the delay.
> >>
> >> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> >
> > Who should pick this up?
> >
> > $ scripts/get_maintainer.pl lib/this.patch says:
> > Andrew Morton <akpm@linux-foundation.org> (commit_signer:8/56=14%)
> > "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> (commit_signer:7/56=12%)
> > Ingo Molnar <mingo@elte.hu> (commit_signer:5/56=9%)
> > Frederic Weisbecker <fweisbec@gmail.com> (commit_signer:5/56=9%)
> > Randy Dunlap <rdunlap@xenotime.net> (commit_signer:3/56=5%)
> 
> Catalin, Randy since lib/Kconfig.debug has no official maintainer
> I think this should go up through your trees.

I hadn't seen it until now, but I can merge it.

thanks.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-03-30 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 18:16 Daniel Baluta
2011-03-23 11:18 ` Daniel Baluta
2011-03-23 11:23   ` Pekka Enberg
2011-03-23 11:24 ` Catalin Marinas
2011-03-25 14:05   ` Daniel Baluta
2011-03-30 15:02     ` Daniel Baluta
2011-03-30 15:24       ` Randy Dunlap [this message]
2011-03-31  7:44         ` Daniel Baluta

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=20110330082419.b782fa94.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=daniel.baluta@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=penberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®