linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Terminator <jimmy@mtc.dhs.org>, linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.14 compiling fail for loop device
Date: 05 Nov 2001 23:02:36 -0500	[thread overview]
Message-ID: <1005019360.897.2.camel@phantasy> (raw)
In-Reply-To: <20011105194316.B665@mikef-linux.matchmail.com>
In-Reply-To: <Pine.LNX.4.33.0111051936090.18663-100000@www.mtc.dhs.org>  <20011105194316.B665@mikef-linux.matchmail.com>

On Mon, 2001-11-05 at 22:43, Mike Fedyk wrote:
> Did anyone have this problem with pre8???

Nope, it was added post-pre8 to final.  The deactivate_page function was
removed completely.

	Robert Love


  parent reply	other threads:[~2001-11-06  4:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06  3:39 kernel 2.4.14 compiling fail for loop device Terminator
2001-11-06  3:43 ` Mike Fedyk
2001-11-06  4:02 ` Robert Love [this message]
2001-11-06  4:08   ` Mohammad A. Haque
2001-11-06  4:14     ` Robert Love
2001-11-06  4:29       ` Mike Fedyk
2001-11-07 12:13     ` Todd M. Roy
2001-11-07 20:49       ` Roeland Th. Jansen
2001-11-07 21:11         ` Mohammad A. Haque
2001-11-07 21:34           ` J Sloan
2001-11-07 11:58             ` rpjday
2001-11-07 21:44               ` J Sloan
2001-11-07 21:41             ` Roeland Th. Jansen
2001-11-07 21:40           ` Roeland Th. Jansen
2001-11-07  3:13   ` Are -final releases realy FINAL? (Was Re: kernel 2.4.14 compiling fail for loop device) Anuradha Ratnaweera
2001-11-07  3:17     ` Mike Fedyk
2001-11-07  3:27       ` Anuradha Ratnaweera
2001-11-07  3:24     ` Michael H. Warfield
2001-11-07  4:06     ` David Lang
     [not found] <no.id>
2001-11-07 15:12 ` kernel 2.4.14 compiling fail for loop device Barry K. Nathan
2001-11-07 15:21   ` Todd M. Roy
2001-11-07 15:38   ` Mohammad A. Haque
2001-11-07 15:48     ` Mohammad A. Haque

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=1005019360.897.2.camel@phantasy \
    --to=rml@tech9.net \
    --cc=jimmy@mtc.dhs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).