From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: 'Greg KH' <gregkh@linuxfoundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
'Ju Hyung Park' <qkrwngud825@gmail.com>,
'Valdis Kletnieks' <valdis.kletnieks@vt.edu>,
devel@driverdev.osuosl.org, linkinjeon@gmail.com,
linux-kernel@vger.kernel.org, alexander.levin@microsoft.com,
sergey.senozhatsky@gmail.com, linux-fsdevel@vger.kernel.org,
sj1557.seo@samsung.com
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to
Date: Wed, 18 Sep 2019 17:51:34 +0900 [thread overview]
Message-ID: <20190918085134.GA47301@jagdpanzerIV> (raw)
In-Reply-To: <20190918082658.GA1861850@kroah.com>
On (09/18/19 10:26), 'Greg KH' wrote:
> On Wed, Sep 18, 2019 at 03:33:04PM +0900, Sergey Senozhatsky wrote:
> > On (09/18/19 08:16), 'Greg KH' wrote:
> > [..]
> > > > Note, that Samsung is still improving sdfat driver. For instance,
> > > > what will be realeased soon is sdfat v2.3.0, which will include support
> > > > for "UtcOffset" of "File Directory Entry", in order to satisfy
> > > > exFAT specification 7.4.
> > >
> > [..]
> > > If Samsung wishes to use their sdfat codebase as the "seed" to work from
> > > for this, please submit a patch adding the latest version to the kernel
> > > tree and we can compare and work from there.
> >
> > Isn't it what Ju Hyung did? He took sdfat codebase (the most recent
> > among publicly available) as the seed, cleaned it up a bit and submitted
> > as a patch.
>
> He did? I do not see a patch anywhere, what is the message-id of it?
Sorry. No, he did not. I somehow thought that he did, but it seems that
I just looked at his github and emails.
> > Well, technically, Valdis did the same, it's just he forked a slightly
> > more outdated (and not anymore used by Samsung) codebase.
>
> He took the "best known at the time" codebase, as we had nothing else to
> work with.
Well, then Valdis probably took it a long long time ago. Current
"best known" is v2.2, publicly available under GPLv2 at opensource.samsung.com
-ss
next prev parent reply other threads:[~2019-09-18 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190917025738epcas1p1f1dd21ca50df2392b0f84f0340d82bcd@epcas1p1.samsung.com>
[not found] ` <003601d56d03$aa04fa00$fe0eee00$@samsung.com>
2019-09-17 3:02 ` [PATCH] staging: exfat: add exfat filesystem code to Namjae Jeon
2019-09-17 4:19 ` Valdis Klētnieks
2019-09-17 5:31 ` Park Ju Hyung
2019-09-17 5:47 ` Greg KH
2019-09-17 6:04 ` Ju Hyung Park
2019-09-18 2:35 ` Namjae Jeon
2019-09-18 6:16 ` 'Greg KH'
2019-09-18 6:33 ` Sergey Senozhatsky
2019-09-18 8:26 ` 'Greg KH'
2019-09-18 8:51 ` Sergey Senozhatsky [this message]
2019-09-18 9:01 ` Ju Hyung Park
2019-09-18 9:24 ` Dan Carpenter
2019-09-18 9:53 ` Ju Hyung Park
2019-09-18 10:08 ` Dan Carpenter
2019-09-18 10:46 ` Ju Hyung Park
2019-09-18 11:05 ` Greg KH
2019-09-19 2:14 ` Namjae Jeon
2019-09-30 4:25 ` Namjae Jeon
2019-09-30 6:08 ` 'Greg KH'
2019-09-17 4:56 ` 'Greg KH'
2019-09-17 5:15 ` Gao Xiang
[not found] <20190828160817.6250-1-gregkh@linuxfoundation.org>
2019-09-14 13:39 ` Park Ju Hyung
2019-09-15 13:54 ` Greg KH
2019-09-15 16:11 ` Ju Hyung Park
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=20190918085134.GA47301@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=alexander.levin@microsoft.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=qkrwngud825@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sj1557.seo@samsung.com \
--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).