From: hpa@transmeta.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: PATCH 2.4.14.2: more inflate_fs build fixes
Date: 26 Oct 2001 09:35:31 -0700 [thread overview]
Message-ID: <9rc3cj$pt$1@tazenda.transmeta.com> (raw)
In-Reply-To: <3BD92F59.BAD76B6F@mandrakesoft.com> <E15x7tg-0000Df-00@the-village.bc.nu>
Followup to: <E15x7tg-0000Df-00@the-village.bc.nu>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> > This is required also, in order to build cramfs or zisofs in
> > 2.4.14-pre2.
>
> I was going to send Linus that too after I grabbed pre2 - thanks.
>
> Alan
>
Also, grab_cache_page_nowait() [mm/filemap.c] is missing in -pre2, so
zisofs still won't build without it. I will look at the new mm code
and try to determine how applicable the code I have is; if not, I
might end up having to contact Andrea for some tips.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
prev parent reply other threads:[~2001-10-26 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 9:39 PATCH 2.4.14.2: more inflate_fs build fixes Jeff Garzik
2001-10-26 14:23 ` Alan Cox
2001-10-26 16:35 ` H. Peter Anvin [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='9rc3cj$pt$1@tazenda.transmeta.com' \
--to=hpa@transmeta.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