From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: kernelnewbies@kernelnewbies.org
Subject: uxfs review
Date: Thu, 20 Feb 2020 18:39:21 +0100 [thread overview]
Message-ID: <20200220173920.GG18366@valentin-vidic.from.hr> (raw)
On Wed, Feb 19, 2020 at 04:36:10PM -0500, Valdis Klētnieks wrote:
> (Of course, if you're trying to get a 2.6.12 driver working on 5.6... you may decide
> that it's time to start drinking heavily :)
Now that you mention 2.6 :), I've been trying to update this uxfs
filesystem from an old book[1] for modern kernels:
https://github.com/vvidic/uxfs/
It currently builds and seems to work but it could probably use a
review if someone has a bit of time? I can post the diff here if
that would be easier.
[1] Steve D. Pate, UNIX Filesystems, 2003.
--
Valentin
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-02-20 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 17:39 Valentin Vidić [this message]
2020-02-20 20:12 ` uxfs review Valdis Klētnieks
2020-02-20 20:33 ` Valentin Vidić
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=20200220173920.GG18366@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).