From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Al Viro <viro@zeniv.linux.org.uk>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 00/41] fs/adfs updates for 5.6
Date: Mon, 9 Dec 2019 11:07:31 +0000 [thread overview]
Message-ID: <20191209110731.GD25745@shell.armlinux.org.uk> (raw)
Hi,
This patch series updates the fs/adfs code in the kernel (which still
has users!)
- update inode timestamps to centisecond resolution time, as per the
native format.
- consolidate and clean up map scanning code.
- consolidate and clean up and modernise directory handling code.
- restructure directory handling code to better improve the rudimentary
write support we have.
- fix inode dropping; otherwise updates are lost on umount.
- add support for E and E+ format image files.
Patches based on v5.4; there have been no changes to fs/adfs during the
merge window.
This is also available from:
git://git.armlinux.org.uk/~rmk/linux-arm.git adfs
with head SHA1 8901af013ecd.
Documentation/filesystems/adfs.txt | 24 +++
fs/adfs/adfs.h | 32 ++--
fs/adfs/dir.c | 314 +++++++++++++++++++++++++--------
fs/adfs/dir_f.c | 302 +++++++++-----------------------
fs/adfs/dir_f.h | 52 +++---
fs/adfs/dir_fplus.c | 345 +++++++++++++++++++++----------------
fs/adfs/dir_fplus.h | 6 +-
fs/adfs/inode.c | 64 +++----
fs/adfs/map.c | 247 +++++++++++++++++++-------
fs/adfs/super.c | 267 ++++++++++------------------
10 files changed, 913 insertions(+), 740 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next reply other threads:[~2019-12-09 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 11:07 Russell King - ARM Linux admin [this message]
2019-12-09 11:11 ` [PATCH 41/41] Documentation: update adfs filesystem documentation Russell King
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=20191209110731.GD25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).