From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
jmoyer@redhat.com, carson@taltos.org,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
davem@redhat.com
Subject: Re: kernel BUG at page_alloc.c:98 -- compiling with distcc
Date: Fri, 30 Apr 2004 00:49:36 +0200 [thread overview]
Message-ID: <20040429224936.GT29954@dualathlon.random> (raw)
In-Reply-To: <20040429142807.1fa4c5ea.akpm@osdl.org>
On Thu, Apr 29, 2004 at 02:28:07PM -0700, Andrew Morton wrote:
> just to exercise that code path a bit more.
what's the point of exercising that code path more? are you worried that
there are bugs in it?
next prev parent reply other threads:[~2004-04-29 22:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 22:33 kernel BUG at page_alloc.c:98 -- compiling with distcc Carson Gaspar
2004-04-28 2:02 ` Jeff Moyer
2004-04-29 21:09 ` Marcelo Tosatti
2004-04-29 21:28 ` Andrew Morton
2004-04-29 22:49 ` Andrea Arcangeli [this message]
2004-04-29 23:26 ` Andrew Morton
2004-04-30 0:15 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 10:21 Marco Fais
2004-04-02 13:15 ` Marco Roeland
[not found] ` <6.0.0.22.2.20040402163334.02abe7d8@pop.localnet>
2004-04-02 15:05 ` Marco Roeland
2004-04-05 10:42 ` Marco Fais
2004-04-05 11:46 ` Marco Roeland
2004-04-05 14:08 ` Marco Fais
2004-04-05 14:36 ` Marco Roeland
2004-04-05 17:03 ` Max Valdez
2004-04-02 23:36 ` Andrew Morton
2004-04-05 10:47 ` Marco Fais
2004-04-05 10:56 ` Andrew Morton
2004-04-05 13:58 ` Marco Fais
2004-05-04 1:07 ` Marcelo Tosatti
2004-05-05 16:25 ` Carson Gaspar
2004-05-05 16:28 ` Marc-Christian Petersen
2004-05-05 18:35 ` Marcelo Tosatti
2004-05-19 11:59 ` Marcelo Tosatti
2004-05-19 15:50 ` Marc-Christian Petersen
2004-05-20 12:21 ` Marcelo Tosatti
2004-05-19 20:21 ` Carson Gaspar
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=20040429224936.GT29954@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=carson@taltos.org \
--cc=davem@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.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