linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	Sankar P <sankar.curiosity@gmail.com>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	lrodriguez@atheros.com, rnagarajan@novell.com, teheo@novell.com,
	linux-mm@kvack.org, paulmck@linux.vnet.ibm.com, mingo@elte.hu,
	akpm@linux-foundation.org
Subject: Re: [PATCH] kmemleak: config-options: Default buffer size for kmemleak
Date: Tue, 22 Jun 2010 15:41:24 +0300	[thread overview]
Message-ID: <AANLkTim-5W0BJ955VkIUpPCrPbXXZdCEkUVOIGeDZGo0@mail.gmail.com> (raw)
In-Reply-To: <1277210104.29532.13.camel@e102109-lin.cambridge.arm.com>

On Tue, Jun 22, 2010 at 3:35 PM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Tue, 2010-06-22 at 13:21 +0100, Pekka Enberg wrote:
>> On Tue, Jun 22, 2010 at 3:05 PM, Catalin Marinas
>> <catalin.marinas@arm.com> wrote:
>> > The defconfig change for this specific platform may be a better option
>> > but I thought defconfigs are to provide a stable (and maybe close to
>> > optimal) configuration without all the debugging features enabled
>> > (especially those slowing things down considerably).
>>
>> The defconfig change was definitely not a clean solution to this
>> problem. Better bake the fix in Kconfig proper even if it means
>> dependency on CONFIG_SH or something.
>
> OK, maybe something like this
>
>        default 1000 if SH
>        default 400
>
> It seems that kbuild only considers the first encounter of "default".

Sure, I'm fine with that.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-22 12:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  9:21 Probable Bug (or configuration error) in kmemleak Sankar P
2010-06-17 17:36 ` Luis R. Rodriguez
2010-06-18  8:11   ` Sankar P
2010-06-18 13:00     ` Catalin Marinas
2010-06-18 13:25       ` Sankar P
2010-06-22  6:54         ` Sankar P
2010-06-22  6:58     ` [PATCH] mm: kmemleak: Change kmemleak default buffer size Sankar P
2010-06-22  8:11       ` Pekka Enberg
2010-06-22  8:46         ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Sankar P
2010-06-22 11:31           ` Paul Mundt
2010-06-22 12:05             ` Catalin Marinas
2010-06-22 12:14               ` Paul Mundt
2010-06-22 12:21               ` Pekka Enberg
2010-06-22 12:35                 ` Catalin Marinas
2010-06-22 12:41                   ` Pekka Enberg [this message]
2010-06-22 16:55       ` [PATCH] mm: kmemleak: Change kmemleak default buffer size Luis R. Rodriguez
2010-06-24  7:31         ` Sankar P
2010-06-24 18:56           ` Luis R. Rodriguez

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=AANLkTim-5W0BJ955VkIUpPCrPbXXZdCEkUVOIGeDZGo0@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rnagarajan@novell.com \
    --cc=sankar.curiosity@gmail.com \
    --cc=teheo@novell.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