From: "Andrew Hatfield" <lkml@secureone.com.au>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.18-pre9-mjc2
Date: Thu, 14 Feb 2002 15:46:53 +1000 [thread overview]
Message-ID: <046e01c1b51b$01a50160$0f01000a@brisbane.hatfields.com.au> (raw)
In-Reply-To: <1013662709.6671.16.camel@ohdarn.net>
got this problem when applying 2.4.18-pre8-mjc to 2.4.18-pre8 to 2.4.17 as
well as newly released 2.4.18-pre8-mjc2
filemap.c: In function `__find_page_nolock':
filemap.c:404: structure has no member named `next_hash'
Not sure if this is related to Rik's rmap patch or Ingo's O(1) Scheduler
patch (or again, something else entirely)
your mjc2 patch contains....
patch-2.4.18-pre9-mjc2:- struct page *next_hash; /* Next page
sharing our hash bucket in
patch-2.4.18-pre9-mjc2:- struct page **pprev_hash; /*
Complement to *next_hash. */
which modifes linux/include/linux/mm.h
if i comment out the line in filemap.c it continues to compile... until
problems with ip.h (more to come)
--
Andrew Hatfield
SecureONE - http://www.secureone.com.au/
President - South East Brisbane Linux Users Group http://www.seblug.org/
Kernel work available at http://development.secureone.com.au/kernel/
next prev parent reply other threads:[~2002-02-14 5:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 4:58 Michael Cohen
2002-02-14 5:09 ` Michael Cohen
2002-02-14 10:26 ` Lionel Bouton
2002-02-14 5:12 ` Andrew Hatfield
2002-02-14 5:19 ` Larry McVoy
2002-02-14 13:58 ` Ed Tomlinson
2002-02-14 5:46 ` Andrew Hatfield [this message]
2002-02-14 5:51 ` William Lee Irwin III
2002-02-14 5:48 ` Michael Cohen
2002-02-14 11:43 ` Matthias Andree
2002-02-14 12:36 ` Alan Cox
2002-02-14 12:34 ` Martin Dalecki
2002-02-17 13:45 ` Pavel Machek
2002-02-18 19:04 ` Alan Cox
2002-02-18 20:58 ` Pavel Machek
2002-02-18 21:16 ` Alan Cox
2002-02-18 21:08 ` Pavel Machek
2002-02-18 21:39 ` Alan Cox
2002-02-18 21:43 ` Kjartan Maraas
2002-02-19 9:22 ` Pavel Machek
2002-02-19 9:47 ` Alan Cox
2002-02-20 11:33 ` Pavel Machek
2002-02-15 3:18 ` Linux 2.4.18-pre9-mjc2 & Rmap12f [PATCH] Mike Fedyk
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='046e01c1b51b$01a50160$0f01000a@brisbane.hatfields.com.au' \
--to=lkml@secureone.com.au \
--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
all inboxes | Powered by JetHome®