From: Pawel Kot <pkot@linuxnews.pl>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-ntfs-dev@lists.sourceforge.net>
Subject: [ANN] NTFS 2.0.7c for Linux 2.4.18
Date: Fri, 17 May 2002 02:57:07 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0205170249300.377-100000@bzzzt.slackware.pl> (raw)
Hi,
As Arek Miskiewicz reported to me, the previous NTFS TNG versions didn't
compile with CONFIG_HIGHMEM. The compilation failed due to lack of the
definition of the KM_BIO_IRQ used in the NTFS code.
In this release KM_BIO_IRQ was added to km_type enum on all platforms
supporting it (sparc, ppm, i386).
If you don't use HIGHMEM support or use other architecture the changes
don't touch you.
The patch is available as always from the linux-ntfs project's page:
http://linux-ntfs.sf.net/downloads.html
As usually big thanks to Anton.
pkot
--
Pawel Kot <pkot@linuxnews.pl>
http://www.gnokii.org/ :: http://www.slackware.pl/
http://kt.linuxnews.pl/ -- Kernel Traffic po polsku
next reply other threads:[~2002-05-17 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 0:57 Pawel Kot [this message]
2002-05-17 14:07 ` [ANN] NTFS 2.0.7c for Linux 2.4.18 Pawel Kot
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=Pine.LNX.4.33.0205170249300.377-100000@bzzzt.slackware.pl \
--to=pkot@linuxnews.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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).