![]() | |||||||||||||
Messages in this thread |
Correct fix is to remove __find_page_nolock entirely. On Thu, 2002-02-14 at 00:46, Andrew Hatfield wrote: > 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/ > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:24 [from the cache] ©2003-2008 | |||||||||||||