From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Sasha Levin" <sashal@kernel.org>,
devel@driverdev.osuosl.org,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"Christoph Hellwig" <hch@infradead.org>,
linux-kernel@vger.kernel.org,
"Sasha Levin" <alexander.levin@microsoft.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to staging
Date: Wed, 16 Oct 2019 09:22:11 -0700 [thread overview]
Message-ID: <20191016162211.GA505532@kroah.com> (raw)
In-Reply-To: <20191016160349.pwghlg566hh2o7id@pali>
On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote:
> > Can I assume you will be implementing TexFAT support once the spec is
> > available?
>
> I cannot promise that I would implement something which I do not know
> how is working... It depends on how complicated TexFAT is and also how
> future exfat support in kernel would look like.
>
> But I'm interesting in implementing it.
What devices need TexFAT? I thought it the old devices that used it are
long obsolete and gone. How is this feature going to be tested/used?
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2019-10-16 16:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190828160817.6250-1-gregkh@linuxfoundation.org>
[not found] ` <20190829205631.uhz6jdboneej3j3c@pali>
2019-08-30 15:40 ` [PATCH] staging: exfat: add exfat filesystem code to staging Christoph Hellwig
2019-08-30 15:43 ` Pali Rohár
[not found] ` <184209.1567120696@turing-police>
[not found] ` <20190829233506.GT5281@sasha-vm>
[not found] ` <20190830075647.wvhrx4asnkrfkkwk@pali>
2019-10-16 14:03 ` Pali Rohár
2019-10-16 14:31 ` Sasha Levin
2019-10-16 16:03 ` Pali Rohár
2019-10-16 16:20 ` Sasha Levin
2019-10-16 16:22 ` Greg Kroah-Hartman [this message]
2019-10-16 16:32 ` Pali Rohár
2019-10-16 16:50 ` Greg Kroah-Hartman
2019-10-16 20:33 ` Sasha Levin
2019-10-16 21:53 ` Valdis Klētnieks
2019-10-17 7:53 ` Pali Rohár
2019-10-17 7:50 ` Pali Rohár
2020-02-13 0:06 ` Pali Rohár
2020-02-13 21:18 ` Sasha Levin
2020-02-14 22:16 ` Valdis Klētnieks
2020-02-14 22:43 ` Pali Rohár
2020-02-14 23:25 ` Valdis Klētnieks
2020-04-21 21:30 ` exfat upcase table for code points above U+FFFF (Was: Re: [PATCH] staging: exfat: add exfat filesystem code to staging) Pali Rohár
2020-04-27 15:49 ` Sasha Levin
2020-04-28 7:46 ` Pali Rohár
2019-10-16 16:05 ` [PATCH] staging: exfat: add exfat filesystem code to staging Valdis Klētnieks
[not found] ` <20190828170022.GA7873@kroah.com>
[not found] ` <20190829062340.GB3047@infradead.org>
[not found] ` <20190829063955.GA30193@kroah.com>
[not found] ` <20190829094136.GA28643@infradead.org>
[not found] ` <20190829095019.GA13557@kroah.com>
[not found] ` <20190829103749.GA13661@infradead.org>
[not found] ` <20190829111810.GA23393@kroah.com>
2019-08-30 15:36 ` Christoph Hellwig
2019-08-30 21:54 ` Dave Chinner
2019-08-31 10:31 ` Valdis Klētnieks
2019-09-01 0:04 ` Dave Chinner
[not found] ` <20190829151144.GJ23584@kadam>
[not found] ` <20190829152757.GA125003@architecture4>
[not found] ` <20190829154346.GK23584@kadam>
[not found] ` <cd38b645-2930-3e02-6c6a-5972ea02b537@huawei.com>
[not found] ` <20190830115142.GM2752@twin.jikos.cz>
2019-08-31 3:50 ` Chao Yu
2019-09-14 13:39 ` [PATCH] staging: exfat: add exfat filesystem code to Park Ju Hyung
2019-09-15 13:54 ` Greg KH
2019-09-15 16:11 ` Ju Hyung Park
[not found] ` <20190918195920.25210-1-qkrwngud825@gmail.com>
2019-09-18 20:12 ` [PATCH] staging: exfat: rebase to sdFAT v2.2.0 Greg KH
2019-09-18 20:13 ` Greg KH
2019-09-18 20:22 ` Ju Hyung Park
2019-09-18 20:26 ` Greg KH
2019-09-18 20:31 ` Ju Hyung Park
2019-09-18 20:46 ` Valdis Klētnieks
2019-09-18 21:31 ` kbuild test robot
2019-09-18 21:31 ` kbuild test robot
2019-09-18 22:17 ` Ju Hyung Park
2019-10-24 9:39 ` [PATCH] staging: exfat: add exfat filesystem code to staging 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=20191016162211.GA505532@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=devel@driverdev.osuosl.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sashal@kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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).