From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: mremap sleeping in incorrect context
Date: 01 Aug 2003 12:41:25 +0200 [thread overview]
Message-ID: <1059734484.8194.45.camel@gaston> (raw)
In-Reply-To: <20030731145132.64ab1574.akpm@osdl.org>
On Thu, 2003-07-31 at 23:51, Andrew Morton wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> >
> >
> > > oops. What are your CONFIG_HIGHMEM and CONFIG_HIGHPTE settings there?
> >
> > this is on ppc32, HIGHPTE doesn't exist, HIGHMEM is enabled (1Gb of
> > RAM)
> >
>
> OK, thanks. Seems that I made a little bug. This should fix it. With a
> changelog like this, it _has_ to be right ;)
Thanks, I'll apply here and let you know if this warning is really gone
after a couple of days of use...
Ben.
prev parent reply other threads:[~2003-08-01 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 17:32 mremap sleeping in incorrect context Benjamin Herrenschmidt
2003-07-30 22:34 ` Andrew Morton
2003-07-31 13:38 ` Benjamin Herrenschmidt
2003-07-31 21:51 ` Andrew Morton
2003-08-01 10:41 ` Benjamin Herrenschmidt [this message]
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=1059734484.8194.45.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).