From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: davidm@hpl.hp.com, alan@lxorguk.ukuu.org.uk, akpm@zip.com.au,
linux-kernel@vger.kernel.org
Subject: Re: proc_misc.c bug
Date: Fri, 11 Apr 2003 11:32:39 -0700 [thread overview]
Message-ID: <16023.2631.748820.401393@napali.hpl.hp.com> (raw)
In-Reply-To: <20030411102946.685a907c.rddunlap@osdl.org>
>>>>> On Fri, 11 Apr 2003 10:29:46 -0700, "Randy.Dunlap" <rddunlap@osdl.org> said:
Randy> For kmalloc() failing, do you mean the first (large)
Randy> kmalloc() or the repeated ones that grow in size each time?
I was concerned about the kmalloc() in interrupts_open().
--david
next prev parent reply other threads:[~2003-04-11 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 22:02 David Mosberger
2003-04-10 21:44 ` Alan Cox
2003-04-10 22:49 ` Randy.Dunlap
2003-04-11 5:01 ` Randy.Dunlap
2003-04-11 5:28 ` Andrew Morton
2003-04-11 5:41 ` David Mosberger
2003-04-11 5:46 ` Zwane Mwaikambo
2003-04-11 17:29 ` Randy.Dunlap
2003-04-11 18:32 ` David Mosberger [this message]
2003-04-10 22:53 ` Andrew Morton
2003-04-11 0:27 ` David Mosberger
2003-04-10 22:18 ` Andrew Morton
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=16023.2631.748820.401393@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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®