Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu>
To:     "Namjae Jeon" <namjae.jeon@samsung.com>
Cc:     "'Greg KH'" <gregkh@linuxfoundation.org>,
        alexander.levin@microsoft.com, devel@driverdev.osuosl.org,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        sergey.senozhatsky@gmail.com, "Namjae Jeon" <linkinjeon@gmail.com>
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to
In-Reply-To: <003701d56d04$470def50$d529cdf0$@samsung.com>
References: <CGME20190917025738epcas1p1f1dd21ca50df2392b0f84f0340d82bcd@epcas1p1.samsung.com> <003601d56d03$aa04fa00$fe0eee00$@samsung.com>
 <003701d56d04$470def50$d529cdf0$@samsung.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1568693976_2440P";
         micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date:   Tue, 17 Sep 2019 00:19:36 -0400
Message-ID: <8998.1568693976@turing-police>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--==_Exmh_1568693976_2440P
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Tue, 17 Sep 2019 12:02:01 +0900, =22Namjae Jeon=22 said:
> We are excited to see this happening and would like to state that we ap=
preciate time and
> effort which people put into upstreaming exfat. Thank you=21

The hard part - getting Microsoft to OK merging an exfat driver - is done=
.

All we need now is to get a driver cleaned up. :)

> However, if possible, can we step back a little bit and re-consider it?=
 We would prefer to
> see upstream the code which we are currently using in our products - sd=
fat - as
> this can be mutually benefitial from various points of view.

I'm working off a somewhat cleaned up copy of Samsung's original driver,
because that's what I had knowledge of.  If the sdfat driver is closer to=
 being
mergeable, I'd not object if that got merged instead.

But here's the problem... Samsung has their internal sdfat code, Park Yu =
Hyung
has what appears to be a fork of that code from some point (and it's uncl=
ear ,
and it's unclear which one has had more bugfixes and cleanups to get it t=
o
somewhere near mainline mergeable.

Can you provide a pointer to what Samsung is *currently* using? We probab=
ly
need to stop and actually look at the code bases and see what's in the be=
st
shape currently.


--==_Exmh_1568693976_2440P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.9.0 11/07/2018

iQIVAwUBXYBe1wdmEQWDXROgAQIoqRAAm8jm/cfHwLtmt/GjplQFdaIBNROwXTcR
OTCa7aqyK0BzgwO9cDqRMwbGEDaN3ywuY6N9YqPsmhZfvZi57390XSXohlsbURw4
Q1ejw0aOlcKdzmSJJCm6/WMGE+DDLXTyDLowzTNXz39RfRx0y4bGu0JKiFr2QJh8
NaB1XRYo1BurpgyiwuWIqI+jrAEa1VvuSDSWSO/EL8BbJbxGbxJPnmjBkkLSpJlW
BnCTqr7ABrKSibxTGOeoDf/yX3Ce04HU11XBPoHNHqR8f1iUHZaCP6IhBUoxofAM
is3h8PZ/6e1YiME83PHpK4vllzcChhdVk9mxcMxMEpIzsIPLN70jQDhZ3z1G7iC2
eYRtkmBtBhdpDQt6CIQYwEffJB2X9yrfLNIhB5tw+IH94Eh4TgHiPFqxtEHlVSaT
WFHhyN954V+PAWL1brma3rxdY+xOK+IEOnY5DM5bW/c+YeJAIrur2c4iZLVHSRTH
kO0bFYOZ41WPThEJnyzzbtMz9HX0WdR+4A5QqIHnoqnmaTKviMAiMeAlor3rlrjk
RzfSfJUJ7oxOQVPpxCIB0/YJ+HtHXR9nEgKHvdCMmyCfb6/Pq2dqJrqQu9YbUPoW
NlRunOynwSQ5ipVKHwmwGTWyjeprRDzfMUObln77rUI03K8Vtap1he0fmjXlZTFl
x0yeZPkfRJk=
=mJjz
-----END PGP SIGNATURE-----

--==_Exmh_1568693976_2440P--