[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <008c01d56e90$01420eb0$03c62c10$@samsung.com>
Date: Thu, 19 Sep 2019 11:14:45 +0900
From: "Namjae Jeon" <namjae.jeon@...sung.com>
To: "'Dan Carpenter'" <dan.carpenter@...cle.com>,
"'Greg KH'" <gregkh@...uxfoundation.org>
Cc: "'Greg KH'" <gregkh@...uxfoundation.org>,
<devel@...verdev.osuosl.org>, <linkinjeon@...il.com>,
"'Valdis Kletnieks'" <valdis.kletnieks@...edu>,
"'Sergey Senozhatsky'" <sergey.senozhatsky.work@...il.com>,
<linux-kernel@...r.kernel.org>, <alexander.levin@...rosoft.com>,
<sergey.senozhatsky@...il.com>, <linux-fsdevel@...r.kernel.org>,
<sj1557.seo@...sung.com>, "'Ju Hyung Park'" <qkrwngud825@...il.com>
Subject: RE: [PATCH] staging: exfat: add exfat filesystem code to
[..]
> 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:)
Thanks!
>
> regards,
> dan carpenter
>
Powered by blists - more mailing lists