From: Anton Altaparmakov <aia21@cantab.net>
To: Pawel Kot <pkot@echelon.pl>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK-2.4 PATCH] Fix compile with highmem and highio
Date: Sat, 24 Aug 2002 16:11:59 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20020824160921.00aeb550@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0208241603390.7446-100000@urtica.linuxnews.p l>
At 15:08 24/08/02, Pawel Kot wrote:
>On Fri, 23 Aug 2002, Anton Altaparmakov wrote:
>
> > Remove duplicate & bogus kmap_prot and kmap_pte exports.
> > These are arch specific and only four architectures implement them. So
> > on all other orchitectures with highmem enabled compilation would
> fail with
> > these exports in ksyms.c...
>
>No, only these 4 architectures allow to set HIGHMEM. So no failure here.
>
> > The architectures which need them already export them via their
> arch-ksyms files.
>
>No. They don't. At least in 2.4.20-pre4. I think they may be exported in
>your tree, because of the ntfs backport patch.
Oops. You are right. I need to reclone a clean 2.4 tree. Mine has somehow
managed to gain a few "extra" changesets. Ahem.
Sorry for the noise.
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
prev parent reply other threads:[~2002-08-24 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 23:47 Anton Altaparmakov
2002-08-24 14:08 ` Pawel Kot
[not found] ` <Pine.LNX.4.33.0208241603390.7446-100000@urtica.linuxnews.p l>
2002-08-24 15:11 ` Anton Altaparmakov [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=5.1.0.14.2.20020824160921.00aeb550@pop.cus.cam.ac.uk \
--to=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pkot@echelon.pl \
/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®