mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmemcheck: Disable SLUB and SLAB debugging when kmemcheck  is enabled
Date: Thu, 26 Feb 2009 09:16:10 +0100	[thread overview]
Message-ID: <19f34abd0902260016x1b354583o418d5f77fe51ae4e@mail.gmail.com> (raw)
In-Reply-To: <1235632643.5465.0.camel@penberg-laptop>

2009/2/26 Pekka Enberg <penberg@cs.helsinki.fi>:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
> Date: Mon, 23 Feb 2009 11:35:13 +0200
> Subject: [PATCH] kmemcheck: Disable SLUB and SLAB debugging when kmemcheck is enabled
>
> Enabling kmemcheck in Kconfig is a painful experience. Lets make it a
> tad bit easier by inverting the dependencies to SLUB and SLAB debugging.
> As kmemcheck is more powerful than slab debugging, disable the latter
> functionality if an user enables kmemcheck.
>
> Cc: Vegard Nossum <vegard.nossum@gmail.com>
> Cc: Christoph Lameter <cl@linux-foundation.org>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>

Thanks, applied!


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

      reply	other threads:[~2009-02-26  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23  9:35 Pekka Enberg
2009-02-23 15:25 ` Sitsofe Wheeler
2009-02-23 15:41 ` Christoph Lameter
2009-02-23 17:33   ` Pekka Enberg
2009-02-25 19:17     ` Vegard Nossum
2009-02-25 21:23       ` Christoph Lameter
2009-02-26  7:17         ` Pekka Enberg
2009-02-26  8:16           ` Vegard Nossum [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=19f34abd0902260016x1b354583o418d5f77fe51ae4e@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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®