From: Valdis Kletnieks <valdis.kletnieks@vt.edu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
linux-fsdevel@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 00/12] staging: exfat: Heave FAT/VFAT over the side
Date: Tue, 12 Nov 2019 16:12:26 -0500 [thread overview]
Message-ID: <20191112211238.156490-1-Valdis.Kletnieks@vt.edu> (raw)
The first 4 patches iteratively remove more and more of the
FAT/VFAT code.
The second 8 patches make a lot of functions static, and
renames many of the rest to avoid namespace pollution.
Valdis Kletnieks (12):
staging: exfat: Remove FAT/VFAT mount support, part 1
staging: exfat: Remove FAT/VFAT mount support, part 2
staging: exfat: Remove FAT/VFAT mount support, part 3
staging: exfat: Remove FAT/VFAT mount support, part 4
staging: exfat: Clean up the namespace pollution part 1
staging: exfat: Clean up the namespace pollution part 2
staging: exfat: Clean up the namespace pollution part 3
staging: exfat: Clean up the namespace pollution part 4
staging: exfat: Clean up the namespace pollution part 5
staging: exfat: Clean up the namespace pollution part 6
staging: exfat: Clean up the namespace pollution part 7
staging: exfat: Clean up the namespace pollution part 8
drivers/staging/exfat/Kconfig | 9 -
drivers/staging/exfat/exfat.h | 160 +--
drivers/staging/exfat/exfat_blkdev.c | 10 +-
drivers/staging/exfat/exfat_cache.c | 251 +---
drivers/staging/exfat/exfat_core.c | 1896 ++++++--------------------
drivers/staging/exfat/exfat_nls.c | 192 ---
drivers/staging/exfat/exfat_super.c | 359 ++---
7 files changed, 595 insertions(+), 2282 deletions(-)
--
2.24.0
next reply other threads:[~2019-11-12 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 21:12 Valdis Kletnieks [this message]
2019-11-12 21:12 ` [PATCH 01/12] staging: exfat: Remove FAT/VFAT mount support, part 1 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 02/12] staging: exfat: Remove FAT/VFAT mount support, part 2 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 03/12] staging: exfat: Remove FAT/VFAT mount support, part 3 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 04/12] staging: exfat: Remove FAT/VFAT mount support, part 4 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 05/12] staging: exfat: Clean up the namespace pollution part 1 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 06/12] staging: exfat: Clean up the namespace pollution part 2 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 07/12] staging: exfat: Clean up the namespace pollution part 3 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 08/12] staging: exfat: Clean up the namespace pollution part 4 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 09/12] staging: exfat: Clean up the namespace pollution part 5 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 10/12] staging: exfat: Clean up the namespace pollution part 6 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 11/12] staging: exfat: Clean up the namespace pollution part 7 Valdis Kletnieks
2019-11-12 21:12 ` [PATCH 12/12] staging: exfat: Clean up the namespace pollution part 8 Valdis Kletnieks
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=20191112211238.156490-1-Valdis.Kletnieks@vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).