From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Sankar P <sankar.curiosity@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"penberg@cs.helsinki.fi" <penberg@cs.helsinki.fi>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"rnagarajan@novell.com" <rnagarajan@novell.com>,
"teheo@novell.com" <teheo@novell.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: kmemleak: Change kmemleak default buffer size
Date: Thu, 24 Jun 2010 18:56:14 +0000 [thread overview]
Message-ID: <20100624185614.GA6031@tux> (raw)
In-Reply-To: <AANLkTikHiPKPD5myvn8bycPAS4f9rBkPvbag6if7p23O@mail.gmail.com>
On Thu, Jun 24, 2010 at 12:31:11AM -0700, Sankar P wrote:
> On Tue, Jun 22, 2010 at 10:25 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Mon, Jun 21, 2010 at 11:58:29PM -0700, Sankar P wrote:
> >> If we try to find the memory leaks in kernel that is
> >> compiled with 'make defconfig', the default buffer size
> >> seem to be inadequate. Change the buffer size from
> >> 400 to 1000, which is sufficient in most cases.
> >>
> >> Signed-off-by: Sankar P <sankar.curiosity@gmail.com>
> >
> > What's your full name? Please read the "Developer's Certificate of Origin 1.1"
> > It says:
> >
> > then you just add a line saying
> >
> > Signed-off-by: Random J Developer <random@developer.example.org>
> >
> > using your real name (sorry, no pseudonyms or anonymous contributions.)
> >
> >
> > Also you may want to post on a new thread instead of using this old thread
> > unless the maintainer is reading this and wants to pick it up.
> >
>
> In our part of the world, we dont have lastnames. We just use the
> first letter of our father's name as the last name.
Oh wow, what part of the world is that? Interesting.
> I will send the updated patch as a new mail, I thought it will be
> easier to follow if all mails belongs to the same thread.
It does help in-thread, but patches should be sent separately unless
you know for sure the maintainer *will* read this.
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Sankar P <sankar.curiosity@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"penberg@cs.helsinki.fi" <penberg@cs.helsinki.fi>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"rnagarajan@novell.com" <rnagarajan@novell.com>,
"teheo@novell.com" <teheo@novell.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: kmemleak: Change kmemleak default buffer size
Date: Thu, 24 Jun 2010 11:56:14 -0700 [thread overview]
Message-ID: <20100624185614.GA6031@tux> (raw)
In-Reply-To: <AANLkTikHiPKPD5myvn8bycPAS4f9rBkPvbag6if7p23O@mail.gmail.com>
On Thu, Jun 24, 2010 at 12:31:11AM -0700, Sankar P wrote:
> On Tue, Jun 22, 2010 at 10:25 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Mon, Jun 21, 2010 at 11:58:29PM -0700, Sankar P wrote:
> >> If we try to find the memory leaks in kernel that is
> >> compiled with 'make defconfig', the default buffer size
> >> seem to be inadequate. Change the buffer size from
> >> 400 to 1000, which is sufficient in most cases.
> >>
> >> Signed-off-by: Sankar P <sankar.curiosity@gmail.com>
> >
> > What's your full name? Please read the "Developer's Certificate of Origin 1.1"
> > It says:
> >
> > then you just add a line saying
> >
> > Signed-off-by: Random J Developer <random@developer.example.org>
> >
> > using your real name (sorry, no pseudonyms or anonymous contributions.)
> >
> >
> > Also you may want to post on a new thread instead of using this old thread
> > unless the maintainer is reading this and wants to pick it up.
> >
>
> In our part of the world, we dont have lastnames. We just use the
> first letter of our father's name as the last name.
Oh wow, what part of the world is that? Interesting.
> I will send the updated patch as a new mail, I thought it will be
> easier to follow if all mails belongs to the same thread.
It does help in-thread, but patches should be sent separately unless
you know for sure the maintainer *will* read this.
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Sankar P <sankar.curiosity@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"penberg@cs.helsinki.fi" <penberg@cs.helsinki.fi>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"rnagarajan@novell.com" <rnagarajan@novell.com>,
"teheo@novell.com" <teheo@novell.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: kmemleak: Change kmemleak default buffer size
Date: Thu, 24 Jun 2010 11:56:14 -0700 [thread overview]
Message-ID: <20100624185614.GA6031@tux> (raw)
In-Reply-To: <AANLkTikHiPKPD5myvn8bycPAS4f9rBkPvbag6if7p23O@mail.gmail.com>
On Thu, Jun 24, 2010 at 12:31:11AM -0700, Sankar P wrote:
> On Tue, Jun 22, 2010 at 10:25 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Mon, Jun 21, 2010 at 11:58:29PM -0700, Sankar P wrote:
> >> If we try to find the memory leaks in kernel that is
> >> compiled with 'make defconfig', the default buffer size
> >> seem to be inadequate. Change the buffer size from
> >> 400 to 1000, which is sufficient in most cases.
> >>
> >> Signed-off-by: Sankar P <sankar.curiosity@gmail.com>
> >
> > What's your full name? Please read the "Developer's Certificate of Origin 1.1"
> > It says:
> >
> > then you just add a line saying
> >
> > Signed-off-by: Random J Developer <random@developer.example.org>
> >
> > using your real name (sorry, no pseudonyms or anonymous contributions.)
> >
> >
> > Also you may want to post on a new thread instead of using this old thread
> > unless the maintainer is reading this and wants to pick it up.
> >
>
> In our part of the world, we dont have lastnames. We just use the
> first letter of our father's name as the last name.
Oh wow, what part of the world is that? Interesting.
> I will send the updated patch as a new mail, I thought it will be
> easier to follow if all mails belongs to the same thread.
It does help in-thread, but patches should be sent separately unless
you know for sure the maintainer *will* read this.
Luis
--
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>
next prev parent reply other threads:[~2010-06-24 18:56 UTC|newest]
Thread overview: 52+ 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-17 17:36 ` Luis R. Rodriguez
2010-06-18 8:11 ` Sankar P
2010-06-18 13:00 ` Catalin Marinas
2010-06-18 13:00 ` Catalin Marinas
2010-06-18 13:25 ` Sankar P
2010-06-18 13:25 ` Sankar P
2010-06-22 6:54 ` 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 6:59 ` Sankar P
2010-06-22 6:58 ` Sankar P
2010-06-22 8:11 ` Pekka Enberg
2010-06-22 8:11 ` Pekka Enberg
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 8:58 ` Sankar P
2010-06-22 8:46 ` Sankar P
2010-06-22 11:31 ` Paul Mundt
2010-06-22 11:31 ` Paul Mundt
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:05 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Catalin Marinas
2010-06-22 12:05 ` Catalin Marinas
2010-06-22 12:14 ` Paul Mundt
2010-06-22 12:14 ` Paul Mundt
2010-06-22 12:14 ` Paul Mundt
2010-06-22 12:21 ` [PATCH] kmemleak: config-options: Default buffer size for Pekka Enberg
2010-06-22 12:21 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Pekka Enberg
2010-06-22 12:21 ` Pekka Enberg
2010-06-22 12:35 ` [PATCH] kmemleak: config-options: Default buffer size for Catalin Marinas
2010-06-22 12:35 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Catalin Marinas
2010-06-22 12:35 ` Catalin Marinas
2010-06-22 12:41 ` [PATCH] kmemleak: config-options: Default buffer size for Pekka Enberg
2010-06-22 12:41 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Pekka Enberg
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-22 16:55 ` Luis R. Rodriguez
2010-06-22 16:55 ` Luis R. Rodriguez
2010-06-24 7:31 ` Sankar P
2010-06-24 7:43 ` Sankar P
2010-06-24 7:31 ` Sankar P
2010-06-24 18:56 ` Luis R. Rodriguez [this message]
2010-06-24 18:56 ` Luis R. Rodriguez
2010-06-24 18:56 ` Luis R. Rodriguez
[not found] ` <AANLkTim4mjw0BFshK_4RS6oDLLQMH_BF7BklU7EhETSj@mail.gmail.com>
2010-06-24 19:12 ` Luis R. Rodriguez
2010-06-24 19:17 ` Sankar P
2010-06-24 19:20 ` Luis R. Rodriguez
2010-06-24 19:27 ` Sankar P
2010-06-25 9:10 ` Luis R. Rodriguez
2010-06-25 9:18 ` Tejun Heo
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=20100624185614.GA6031@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--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=penberg@cs.helsinki.fi \
--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 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.