From: 'Greg KH' <gregkh@linuxfoundation.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: 'Dan Carpenter' <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, linkinjeon@gmail.com,
'Valdis Kletnieks' <valdis.kletnieks@vt.edu>,
'Sergey Senozhatsky' <sergey.senozhatsky.work@gmail.com>,
'Ju Hyung Park' <qkrwngud825@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: Mon, 30 Sep 2019 08:08:15 +0200 [thread overview]
Message-ID: <20190930060815.GA2029292@kroah.com> (raw)
In-Reply-To: <042701d57747$0e200320$2a600960$@samsung.com>
On Mon, Sep 30, 2019 at 01:25:13PM +0900, Namjae Jeon wrote:
>
> > [..]
> > > Put it in drivers/staging/sdfat/.
> > >
> > > But really we want someone from Samsung to say that they will treat
> > > the staging version as upstream. It doesn't work when people apply
> > > fixes to their version and a year later back port the fixes into
> > > staging. The staging tree is going to have tons and tons of white space
> > > fixes so backports are a pain. All development needs to be upstream
> > > first where the staging driver is upstream. Otherwise we should just
> > > wait for Samsung to get it read to be merged in fs/ and not through the
> > > staging tree.
> > Quite frankly,
> > This whole thing came as a huge-huge surprise to us, we did not initiate
> > upstreaming of exfat/sdfat code and, as of this moment, I'm not exactly
> > sure that we are prepared for any immediate radical changes to our internal
> > development process which people all of a sudden want from us. I need to
> > discuss with related people on internal thread.
> > please wait a while:)
> We decide to contribute sdfat directly and treat upstream exfat.
> Perhaps more time is needed for patch preparation(exfat rename + vfat removal
> + clean-up) and internal processes. After contributing sdfat v2.2.0 as the base,
> We will also provide change-set of sdfat v2.3.0 later.
That's wonderful to hear! If you need help getting patches into
mergable shape, just let us know.
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-30 14:08 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' [this message]
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=20190930060815.GA2029292@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=dan.carpenter@oracle.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=qkrwngud825@gmail.com \
--cc=sergey.senozhatsky.work@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).