From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: pmarques@grupopie.com, linux-kernel@vger.kernel.org, yum.rayan@gmail.com
Subject: Re: RFC: turn kmalloc+memset(,0,) into kcalloc
Date: Fri, 8 Apr 2005 12:49:55 -0700 [thread overview]
Message-ID: <20050408124955.6b36048e.rddunlap@osdl.org> (raw)
In-Reply-To: <20050408194355.GH15688@stusta.de>
On Fri, 8 Apr 2005 21:43:55 +0200 Adrian Bunk wrote:
| On Fri, Apr 08, 2005 at 05:24:42PM +0100, Paulo Marques wrote:
| > Adrian Bunk wrote:
| > >[...]
| > >>>On Tue, Apr 05, 2005 at 05:26:31PM +0100, Paulo Marques wrote:
| > >>
| > >>Hi Adrian,
| > >
| >...
| > >Joerg's list of recursions should be valid independent of the kernel
| > >version. Fixing any real stack problems [1] that might be in this list
| > >is a valuable task.
| > >
| > >And "make checkstack" in a kernel compiled with unit-at-a-time lists
| > >several possible problems at the top.
| >
| > Ok, I've read Jörn's mail also and I think I can help out. It seems
| > however that there are more people working on this. Will it be better to
| > coordinate so we don't duplicate efforts or is the "everyone looks at
| > everything" approach better, so that its harder to miss something?
|
| The only other person that seemed very interested n stack issues was
| Yum Rayan <yum.rayan@gmail.com>.
Well, I am, but they are not high on my list right now,
so no coordination is needed with me currently.
| You could coordinate with him, but in the end it should be possible to
| have a first set of patches ready a few hours or even minutes after you
| started, so duplicate efforts would require a very unlucky timing.
|
| > Paulo Marques
|
| cu
| Adrian
---
~Randy
next prev parent reply other threads:[~2005-04-08 19:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 16:26 Paulo Marques
2005-04-05 18:00 ` Jörn Engel
2005-04-06 12:09 ` Denis Vlasenko
2005-04-05 18:54 ` Jesper Juhl
2005-04-05 19:20 ` Roland Dreier
2005-04-05 20:01 ` Jesper Juhl
2005-04-06 11:28 ` Jörn Engel
2005-04-06 12:15 ` Paulo Marques
2005-04-06 13:10 ` Pekka Enberg
2005-04-06 15:50 ` Paulo Marques
2005-04-07 23:54 ` Kyle Moffett
2005-04-09 2:11 ` Jesper Juhl
2005-04-07 21:47 ` Adrian Bunk
2005-04-08 12:38 ` Paulo Marques
2005-04-08 13:00 ` Adrian Bunk
2005-04-08 13:20 ` Jörn Engel
2005-04-08 13:29 ` Adrian Bunk
2005-04-08 16:24 ` Paulo Marques
2005-04-08 19:43 ` Adrian Bunk
2005-04-08 19:49 ` Randy.Dunlap [this message]
2005-04-08 13:00 ` stack checking (was: Re: RFC: turn kmalloc+memset(,0,) into kcalloc) Jörn Engel
2005-04-09 14:19 ` RFC: turn kmalloc+memset(,0,) into kcalloc Paul Jackson
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=20050408124955.6b36048e.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=yum.rayan@gmail.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
all inboxes | Powered by JetHome®