[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191016140353.4hrncxa5wkx47oau@pali>
Date: Wed, 16 Oct 2019 16:03:53 +0200
From: Pali Rohár <pali.rohar@...il.com>
To: Sasha Levin <sashal@...nel.org>
Cc: Valdis Klētnieks <valdis.kletnieks@...edu>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
Sasha Levin <alexander.levin@...rosoft.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to staging
On Friday 30 August 2019 09:56:47 Pali Rohár wrote:
> On Thursday 29 August 2019 19:35:06 Sasha Levin wrote:
> > With regards to missing specs/docs/whatever - our main concern with this
> > release was that we want full interoperability, which is why the spec
> > was made public as-is without modifications from what was used
> > internally. There's no "secret sauce" that Microsoft is hiding here.
>
> Ok, if it was just drop of "current version" of documentation then it
> makes sense.
>
> > How about we give this spec/code time to get soaked and reviewed for a
> > bit, and if folks still feel (in a month or so?) that there are missing
> > bits of information related to exfat, I'll be happy to go back and try
> > to get them out as well.
Hello Sasha!
Now one month passed, so do you have some information when missing parts
of documentation like TexFAT would be released to public?
> Basically external references in that released exFAT specification are
> unknown / not released yet. Like TexFAT. So if you have an input in MS
> could you forward request about these missing bits?
--
Pali Rohár
pali.rohar@...il.com
Powered by blists - more mailing lists