From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
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, "Pali Rohár" <pali@kernel.org>,
"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: Tue, 10 Mar 2020 07:18:59 -0400 [thread overview]
Message-ID: <35151.1583839139@turing-police> (raw)
In-Reply-To: <20200310105421.GA2810679@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
On Tue, 10 Mar 2020 11:54:21 +0100, Greg Kroah-Hartman said:
> 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>
You can stick my Acked-by: on that. :)
And thanks to Namjae Jeon for graciously offering to take it off my hands
by providing a better version, and to all the people at Linux Foundation
and Microsoft who did a lot of behind the scenes work to make it happen...
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-03-10 11:57 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 [this message]
2020-03-11 22:47 ` Pali Rohár
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=35151.1583839139@turing-police \
--to=valdis.kletnieks@vt.edu \
--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=pali@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sj1557.seo@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.