From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Dave Airlie <airlied@gmail.com>,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] vmalloc_32 should use GFP_KERNEL
Date: Wed, 18 Jul 2007 16:49:14 +1000 [thread overview]
Message-ID: <1184741354.25235.222.camel@localhost.localdomain> (raw)
In-Reply-To: <20070717233358.2edeaac0.akpm@linux-foundation.org>
On Tue, 2007-07-17 at 23:33 -0700, Andrew Morton wrote:
> whoops, yes.
>
> Are those errors serious and common enough for 2.6.22.x?
No idea, so far, the nouveau DRM isn't something I would recommend to
people to use in stable environments but heh... I don't know who else
uses vmalloc_32.
Cheers,
Ben.
--
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:[~2007-07-18 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 6:25 Benjamin Herrenschmidt
2007-07-18 6:33 ` Andrew Morton
2007-07-18 6:49 ` Benjamin Herrenschmidt [this message]
2007-07-18 10:54 ` Alan Cox
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=1184741354.25235.222.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=airlied@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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