From: 'Greg KH' <gregkh@linuxfoundation.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: devel@driverdev.osuosl.org, Namjae Jeon <linkinjeon@gmail.com>,
'Valdis Kletnieks' <valdis.kletnieks@vt.edu>,
linux-kernel@vger.kernel.org, alexander.levin@microsoft.com,
sergey.senozhatsky@gmail.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to
Date: Tue, 17 Sep 2019 06:56:40 +0200 [thread overview]
Message-ID: <20190917045640.GA2055638@kroah.com> (raw)
In-Reply-To: <003701d56d04$470def50$d529cdf0$@samsung.com>
On Tue, Sep 17, 2019 at 12:02:01PM +0900, Namjae Jeon wrote:
> We are excited to see this happening and would like to state that we appreciate
> time and
> effort which people put into upstreaming exfat. Thank you!
>
> 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 - sdfat - as this can be mutually benefitial from various
> points of view.
What is "different" in it from the code that is currently in linux-next?
What is supported "better"? The code we have today seems to work for
people, so what are we missing here?
Also, submitting patches for this codebase to bring it up to the level
of functionality you need would be wonderful, can you do that?
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-09-17 4:56 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
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' [this message]
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=20190917045640.GA2055638@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=devel@driverdev.osuosl.org \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sergey.senozhatsky@gmail.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).