mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ishan Jayawardena" <ioshadij@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: missing function used in 2.4.14 loop.c
Date: Mon, 19 Nov 2001 17:13:44 +0000	[thread overview]
Message-ID: <F150hjJ8uT6Ssuot0OU00001453@hotmail.com> (raw)

        I've seen that the compilation of off-the-server
2.4.14 tree fails at the end of 'make bzImage' because
drivers/block/loop.c uses the deactivate_page() function,
which seems to have been removed from the source tree.
        By following the progress of the kernel through
2.4.12, 2.4.13, and 2.4.14 patches, I've seen that
page_cache_release() does the same things as
deactivate_page(). Both these functions are used in the
together twice in drivers/block/loop.c. I compiled
the 2.4.14 kernel by commenting out the references to
deactivate_page() but leaving page_cache_release(), and
loopback block devs work; but I do not have the resources
to  check it for memory leaks etc.
        I _think_ I have done the right thing, but
would appreciate verification by a regular kernel-
hacker :-)
I searched the net for some reference to this problem,
but couldn't find anything so far.

(The presence of this function _would_ allow a user
to continue with the compilation _if_ loop blk dev support
was selected as a module, correct ? I've compiled loop blk-
dev support in to the kernel.)

****    Please, CC your comments to me.
ioshadij@hotmail.com
.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


                 reply	other threads:[~2001-11-19 17:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=F150hjJ8uT6Ssuot0OU00001453@hotmail.com \
    --to=ioshadij@hotmail.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

all inboxes | Powered by JetHome®