From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 12515FA372B for ; Wed, 16 Oct 2019 20:33:24 +0000 (UTC) Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D360321925 for ; Wed, 16 Oct 2019 20:33:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="XzJv7/wf" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D360321925 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=driverdev-devel-bounces@linuxdriverproject.org Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id E10AE86702; Wed, 16 Oct 2019 20:33:22 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from fraxinus.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LGpu3jtNKRP; Wed, 16 Oct 2019 20:33:21 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by fraxinus.osuosl.org (Postfix) with ESMTP id 5A64186B1A; Wed, 16 Oct 2019 20:33:21 +0000 (UTC) Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by ash.osuosl.org (Postfix) with ESMTP id 2E1D11BF44C for ; Wed, 16 Oct 2019 20:33:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by silver.osuosl.org (Postfix) with ESMTP id 1D794234AA for ; Wed, 16 Oct 2019 20:33:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from silver.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tjcV1vVK37ja for ; Wed, 16 Oct 2019 20:33:19 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by silver.osuosl.org (Postfix) with ESMTPS id 6C6AC20367 for ; Wed, 16 Oct 2019 20:33:19 +0000 (UTC) Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E813A21835; Wed, 16 Oct 2019 20:33:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571257999; bh=sQAsOokFGnvVh7DS3xyle/w6+XO8DmU7j1JEW0OM9Fo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XzJv7/wfqu3xTvxwOOLAHx9YgE0jusDtYf8bb0I8IMrUHsMrMlj4Q7lpfLy+Wxjjp F1Op02SgoaPr3iyJEAflgDFNGr9ja7Na9Nzm4hQfkhXgV6f7LpM4/1ekCf9Xm1Cd3i 8PeRy74qwWNd9UkMoQw3SLDSA3n2pLGjFzo4oQ8w= Date: Wed, 16 Oct 2019 16:33:17 -0400 From: Sasha Levin To: Pali =?iso-8859-1?Q?Roh=E1r?= Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to staging Message-ID: <20191016203317.GU31224@sasha-vm> References: <20190828160817.6250-1-gregkh@linuxfoundation.org> <20190829205631.uhz6jdboneej3j3c@pali> <184209.1567120696@turing-police> <20190829233506.GT5281@sasha-vm> <20190830075647.wvhrx4asnkrfkkwk@pali> <20191016140353.4hrncxa5wkx47oau@pali> <20191016143113.GS31224@sasha-vm> <20191016160349.pwghlg566hh2o7id@pali> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20191016160349.pwghlg566hh2o7id@pali> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: driverdev-devel@linuxdriverproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Driver Project Developer List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devel@driverdev.osuosl.org, Christoph Hellwig , Valdis =?utf-8?Q?Kl=C4=93tnieks?= , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Sasha Levin , linux-fsdevel@vger.kernel.org Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Roh=E1r wrote: >On Wednesday 16 October 2019 10:31:13 Sasha Levin wrote: >> On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Roh=E1r wrote: >> > On Friday 30 August 2019 09:56:47 Pali Roh=E1r wrote: >> > > On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: >> > > > With regards to missing specs/docs/whatever - our main concern wit= h this >> > > > release was that we want full interoperability, which is why the s= pec >> > > > was made public as-is without modifications from what was used >> > > > internally. There's no "secret sauce" that Microsoft is hiding her= e. >> > > >> > > 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 f= or a >> > > > bit, and if folks still feel (in a month or so?) that there are mi= ssing >> > > > 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 par= ts >> > of documentation like TexFAT would be released to public? >> >> Sure, I'll see if I can get an approval to open it up. > >Ok! > >> 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. It looks like the reason this wasn't made public along with the exFAT spec is that TexFAT is pretty much dead - it's old, there are no users we are aware of, and digging it out of it's grave to make it public is actually quite the headache. Is this something you actually have a need for? an entity that has a requirement for TexFAT? I'd would rather spend my time elsewhere than digging TexFAT out of it's grave. Is there anything else in the exFAT spec that is missing (and someone actually wants/uses)? -- = Thanks, Sasha _______________________________________________ devel mailing list devel@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel