From: Pavel B Dudkin <awfee@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: cramfs 2.2.x back-port
Date: Tue, 07 Nov 2000 03:54:59 +0500 [thread overview]
Message-ID: <3A0736C2.5E250C79@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
Hello everybody,
I am fairly new to the kernel programming, in fact it's my first attemt
at it. As an exercise I was trying to back-port cramfs code to the 2.2.x
kernel, and I seem to have succeeded! The only thing still not working
are symlinks. There are 2 routines in the code, cramfs_readlink() and
cramfs_follow_link() which both use new (2.3.x) function
get_cache_page(), which I don't know how to substitute in 2.2.x. If you
guys know this better than I do, I'd be very grateful if you helped me
out. There may be not much reason in back-porting, but I like 2.2.x and
the only feature from 2.4.x I needed was cramfs.
My cramfs 2.2.x patch follows. It is based on 2.3.40 cramfs code. Please
if you answer to this post, CC: me directly, I am not subscribed.
[-- Attachment #2: cramfs-2.2.x-patch.diff.gz --]
[-- Type: application/x-gzip, Size: 47145 bytes --]
reply other threads:[~2000-11-06 22:52 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=3A0736C2.5E250C79@mail.ru \
--to=awfee@mail.ru \
--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