From: Rasmus Andersen <rasmus@jaquet.dk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@digeo.com>, Dave Hansen <haveblue@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: (2.5.43mm1) Unable to handle kernel paging request
Date: Thu, 17 Oct 2002 17:33:26 +0200 [thread overview]
Message-ID: <20021017173326.A16400@jaquet.dk> (raw)
In-Reply-To: <Pine.LNX.4.44.0210170028360.1466-100000@localhost.localdomain>; from hugh@veritas.com on Thu, Oct 17, 2002 at 12:33:15AM +0100
[-- Attachment #1: Type: text/plain, Size: 180 bytes --]
On Thu, Oct 17, 2002 at 12:33:15AM +0100, Hugh Dickins wrote:
> > Does it happen on 2.5.43?
>
> Isn't this covered by Trond's patch below:
This fixed it. Thanks.
Rasmus
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-10-17 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 20:09 (2.5.43mm1) Unable to handle kernel paging request Rasmus Andersen
2002-10-16 20:41 ` Andrew Morton
2002-10-16 20:54 ` Dave Hansen
2002-10-16 23:33 ` Hugh Dickins
2002-10-17 15:33 ` Rasmus Andersen [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=20021017173326.A16400@jaquet.dk \
--to=rasmus@jaquet.dk \
--cc=akpm@digeo.com \
--cc=haveblue@us.ibm.com \
--cc=hugh@veritas.com \
--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