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
Date: Tue, 22 Jun 2010 12:21:14 +0000 [thread overview]
Message-ID: <AANLkTin9ssqksoAvafRdsogmfrDUhShHCF9aCUb7CtCl@mail.gmail.com> (raw)
In-Reply-To: <1277208351.29532.5.camel@e102109-lin.cambridge.arm.com>
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.
next prev parent reply other threads:[~2010-06-22 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimb7rP0rS0OU8nan5uNEhHx_kEYL99ImZ3c8o0D@mail.gmail.com>
2010-06-22 6:59 ` [PATCH] mm: kmemleak: Change kmemleak default buffer size Sankar P
2010-06-22 8:11 ` Pekka Enberg
2010-06-22 8:58 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Sankar P
2010-06-22 11:31 ` Paul Mundt
2010-06-22 12:05 ` [PATCH] kmemleak: config-options: Default buffer size for Catalin Marinas
2010-06-22 12:14 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Paul Mundt
2010-06-22 12:21 ` Pekka Enberg [this message]
2010-06-22 12:35 ` [PATCH] kmemleak: config-options: Default buffer size for Catalin Marinas
2010-06-22 12:41 ` Pekka Enberg
2010-06-22 16:55 ` [PATCH] mm: kmemleak: Change kmemleak default buffer size Luis R. Rodriguez
2010-06-24 7:43 ` 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=AANLkTin9ssqksoAvafRdsogmfrDUhShHCF9aCUb7CtCl@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;
as well as URLs for NNTP newsgroup(s).