[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190918092405.GC2959@kadam>
Date: Wed, 18 Sep 2019 12:24:06 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Ju Hyung Park <qkrwngud825@...il.com>
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>,
Namjae Jeon <namjae.jeon@...sung.com>,
linux-kernel@...r.kernel.org, alexander.levin@...rosoft.com,
sergey.senozhatsky@...il.com, linux-fsdevel@...r.kernel.org,
sj1557.seo@...sung.com
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to
On Wed, Sep 18, 2019 at 06:01:09PM +0900, Ju Hyung Park wrote:
> On Wed, Sep 18, 2019 at 5:33 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> > He did? I do not see a patch anywhere, what is the message-id of it?
>
> I'm just repeating myself at this point, but again, I'm more than
> willing to work on a patch.
> I just want to make it clear on how should I.
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.
regards,
dan carpenter
Powered by blists - more mailing lists