From: Pavel Fedin <sonic.amiga@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-fsdevel@vger.kernel.org
Subject: Corrupted ASFS patch.
Date: Mon, 9 Feb 2009 16:18:39 +0300 [thread overview]
Message-ID: <187c6cc60902090518vf8589a7nb9ee0ad30e618a03@mail.gmail.com> (raw)
Ouch, really sorry. Unfortunately i have Internet access only at work
and they block all ports except HTTP, FTP and (luckily) POP3. So i can
send mail only via web interface.
Documentation says that i can also place the file somewhere on the
Web and provide a link. Here is it:
http://rapidshare.com/files/195946803/asfs-1.0b12_patch_2.6.24.diff.html
As to endianess signing, sorry, i can't help here because actually
i'm not the filesystem's author. The author is Marek Szyprowski
<march@staszic.waw.pl>, he also tried to post this patch some time
ago, but gave up because someone said that SFS patch won't be accepted
because "Linux doesn't need one more exotic FS".
I just adapted the driver to 2.6.24 kernel (this patch works on
2.6.28 without changes).
You can contact him about the details.
next reply other threads:[~2009-02-09 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 13:18 Pavel Fedin [this message]
2009-02-09 13:31 ` Corrupted ASFS patch maximilian attems
2009-02-12 8:24 ` Re[2]: " Pavel Fedin
2009-02-12 9:42 ` Phillip Lougher
2009-02-12 10:52 ` Re[2]: " Pavel Fedin
2009-02-12 16:38 ` Phillip Lougher
2009-02-13 6:53 ` [PATCH 1/9] Amiga SmartFileSystem, revision 2 Pavel Fedin
2009-02-13 6:54 ` [PATCH 2/9] " Pavel Fedin
2009-02-13 6:55 ` [PATCH 3/9] " Pavel Fedin
2009-02-13 6:55 ` [PATCH 4/9] " Pavel Fedin
2009-02-13 6:56 ` [PATCH 5/9] " Pavel Fedin
2009-02-13 6:56 ` [PATCH 6/9] " Pavel Fedin
2009-02-13 6:56 ` [PATCH 7/9] " Pavel Fedin
2009-02-13 6:57 ` [PATCH 8/9] " Pavel Fedin
2009-02-13 6:57 ` [PATCH 9/9] " Pavel Fedin
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=187c6cc60902090518vf8589a7nb9ee0ad30e618a03@mail.gmail.com \
--to=sonic.amiga@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
/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).