From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.4 required=3.0 tests=DATE_IN_PAST_06_12, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF9BEC35280 for ; Mon, 30 Sep 2019 14:08:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9096B21D71 for ; Mon, 30 Sep 2019 14:08:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569852520; bh=kJDFBY2wP/d0mmh5tm8pzMVU9gXTMQMN67O+To4duB0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Eb4yZCTeQxqpxKrIARvQBvH6dlqio4pZxCTV3xQkArtLI1DxsOKPMuA6x5s2faRaC hsQHdezoPKNjzX6iFyKE67RInT3AhY1rM6Wt+OEGM0EEFBWiviu/6M5vmpILepzPcW b4lHCXQyKjtfvvsSuL+jA5VryAgB8M4iGLgrUUbc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731650AbfI3OIj (ORCPT ); Mon, 30 Sep 2019 10:08:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:44722 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730266AbfI3OIj (ORCPT ); Mon, 30 Sep 2019 10:08:39 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E2220216F4; Mon, 30 Sep 2019 14:08:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569852517; bh=kJDFBY2wP/d0mmh5tm8pzMVU9gXTMQMN67O+To4duB0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WFs2pEicOoD0eFbTMEmox3Zj14a+LOh1AES0AAwN8AK3RjFftj8O5SVgRQe4T6FuB myb9GKVnlj7vJH9XgCKRlmpt/h3TbOR1ZjLW4s7pGSHVDyjy6ojrXQqcdNq66ZYdcc d7NU//lUG06xyR7eJ4Xs+2AZeIvF7ZeSgAdF0B7U= Date: Mon, 30 Sep 2019 08:08:15 +0200 From: 'Greg KH' To: Namjae Jeon Cc: 'Dan Carpenter' , devel@driverdev.osuosl.org, linkinjeon@gmail.com, 'Valdis Kletnieks' , 'Sergey Senozhatsky' , 'Ju Hyung Park' , 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 Message-ID: <20190930060815.GA2029292@kroah.com> References: <20190917054726.GA2058532@kroah.com> <004401d56dc9$b00fd7a0$102f86e0$@samsung.com> <20190918061605.GA1832786@kroah.com> <20190918063304.GA8354@jagdpanzerIV> <20190918082658.GA1861850@kroah.com> <20190918092405.GC2959@kadam> <042701d57747$0e200320$2a600960$@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <042701d57747$0e200320$2a600960$@samsung.com> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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