From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH NFS 0/3] Cleanup/fix nfs_block_size() and nfs_block_bits()
Date: Sun, 24 Jul 2005 16:36:34 +0200 [thread overview]
Message-ID: <20050724143634.GA19896@lsrfire.ath.cx> (raw)
[PATCH NFS 0/3] Cleanup/fix nfs_block_size() and nfs_block_bits()
The Plan 9 filesystem for Linux had some code which wrongly calculated
the size of blocks. A comment said this code has been taken from NFS.
Patch 3 of this series contains a fix for the bug, the first two patches
are preparation work and shouldn't change the results. I didn't went so
far and actually test the patch, so please be careful. =) Compiles fine
here, at least.
Rene
reply other threads:[~2005-07-24 14:36 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=20050724143634.GA19896@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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®