From: "Pali Rohár" <pali@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 'Linux Next Mailing List' <linux-next@vger.kernel.org>,
'Linux Kernel Mailing List' <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Al Viro <viro@zeniv.linux.org.uk>,
Namjae Jeon <namjae.jeon@samsung.com>,
Sungjong Seo <sj1557.seo@samsung.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] staging: exfat: remove staging version of exfat filesystem
Date: Wed, 11 Mar 2020 23:47:05 +0100 [thread overview]
Message-ID: <20200311224705.z3sn3taxjap67jle@pali> (raw)
In-Reply-To: <20200310105421.GA2810679@kroah.com>
On Tuesday 10 March 2020 11:54:21 Greg Kroah-Hartman wrote:
> Now that there is a "real" solution for exfat in the vfs tree queued up
> to be merged in 5.7-rc1 the "old" exfat code in staging can be removed.
>
> Many thanks to Valdis for doing the work to get this into the tree in
> the first place, it was greatly appreciated.
>
> Cc: Valdis Kletnieks <valdis.kletnieks@vt.edu>
> Cc: Pali Rohár <pali@kernel.org>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Al Viro <viro@ZenIV.linux.org.uk>
> Cc: Namjae Jeon <namjae.jeon@samsung.com>
> Cc: Sungjong Seo <sj1557.seo@samsung.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Pali Rohár <pali@kernel.org>
> ---
> MAINTAINERS | 6 -
> drivers/staging/Kconfig | 2 -
> drivers/staging/Makefile | 1 -
> drivers/staging/exfat/Kconfig | 41 -
> drivers/staging/exfat/Makefile | 10 -
> drivers/staging/exfat/TODO | 69 -
> drivers/staging/exfat/exfat.h | 760 ------
> drivers/staging/exfat/exfat_blkdev.c | 138 --
> drivers/staging/exfat/exfat_cache.c | 514 ----
> drivers/staging/exfat/exfat_core.c | 2529 --------------------
> drivers/staging/exfat/exfat_nls.c | 212 --
> drivers/staging/exfat/exfat_super.c | 3296 --------------------------
> drivers/staging/exfat/exfat_upcase.c | 740 ------
> 13 files changed, 8318 deletions(-)
> delete mode 100644 drivers/staging/exfat/Kconfig
> delete mode 100644 drivers/staging/exfat/Makefile
> delete mode 100644 drivers/staging/exfat/TODO
> delete mode 100644 drivers/staging/exfat/exfat.h
> delete mode 100644 drivers/staging/exfat/exfat_blkdev.c
> delete mode 100644 drivers/staging/exfat/exfat_cache.c
> delete mode 100644 drivers/staging/exfat/exfat_core.c
> delete mode 100644 drivers/staging/exfat/exfat_nls.c
> delete mode 100644 drivers/staging/exfat/exfat_super.c
> delete mode 100644 drivers/staging/exfat/exfat_upcase.c
prev parent reply other threads:[~2020-03-11 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 22:59 linux-next: build warning after merge of the vfs tree Stephen Rothwell
2020-03-09 23:17 ` Pali Rohár
2020-03-09 23:36 ` Namjae Jeon
2020-03-10 10:32 ` 'Greg Kroah-Hartman'
2020-03-10 10:54 ` [PATCH] staging: exfat: remove staging version of exfat filesystem Greg Kroah-Hartman
2020-03-10 11:18 ` Valdis Klētnieks
2020-03-11 22:47 ` Pali Rohár [this message]
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=20200311224705.z3sn3taxjap67jle@pali \
--to=pali@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=sj1557.seo@samsung.com \
--cc=valdis.kletnieks@vt.edu \
--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).