From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Ashay Humane <ashay.humane@gmail.com>
Cc: Reiserfs-List@namesys.com
Subject: Re: Fwd: Error in fs/reiser4/page_cache.c : PG_active not declared
Date: Mon, 26 Jul 2004 15:56:05 +0400 [thread overview]
Message-ID: <4104F155.9080504@namesys.com> (raw)
In-Reply-To: <158e29890407242016c70b3f2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
Hello
Ashay Humane wrote:
> Hi,
> I got the vanilla 2.6.7 kernel .. patched it to 2.6.8-rc2 then patched
> it to 2.6.8-rc2-love2.
>
> After the love patch, I get an error when compiling the kernel:
>
> Undeclared variable PG_active in fs/reiser4/page_cache.c Line 891
>
> There are variables named PG_active_mapped and PG_active_unmapped in other .c
> and .h files. But no PG_active .
>
> Dosent look too bad .. but what should be done ?
>
Please try attached patch
> Thanks
> Ashay
>
> --
> <HAND>
>
>
>
[-- Attachment #2: no-PG_active-bit.diff --]
[-- Type: text/plain, Size: 849 bytes --]
===== page_cache.c 1.304 vs edited =====
--- 1.304/page_cache.c 2004-06-25 12:36:13 +04:00
+++ edited/page_cache.c 2004-07-26 15:53:57 +04:00
@@ -881,14 +881,13 @@
}
printk("%s: page index: %lu mapping: %p count: %i private: %lx\n",
prefix, page->index, page->mapping, page_count(page), page->private);
- printk("\tflags: %s%s%s%s %s%s%s%s %s%s%s%s %s%s%s\n",
+ printk("\tflags: %s%s%s%s %s%s%s %s%s%s%s %s%s%s\n",
page_flag_name(page, PG_locked),
page_flag_name(page, PG_error),
page_flag_name(page, PG_referenced),
page_flag_name(page, PG_uptodate),
page_flag_name(page, PG_dirty),
page_flag_name(page, PG_lru),
- page_flag_name(page, PG_active),
page_flag_name(page, PG_slab),
page_flag_name(page, PG_highmem),
page_flag_name(page, PG_checked),
prev parent reply other threads:[~2004-07-26 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <158e298904072418267b1c40d7@mail.gmail.com>
2004-07-25 3:16 ` Fwd: Error in fs/reiser4/page_cache.c : PG_active not declared Ashay Humane
2004-07-25 6:32 ` Maciejewski, Jake
2004-07-26 11:56 ` Vladimir V. Saveliev [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=4104F155.9080504@namesys.com \
--to=vs@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=ashay.humane@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.