Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6229151ybe; Tue, 17 Sep 2019 23:23:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqzhFdtm1gP7tg4wg/FdjihAIeG3JFPkSH/lUclE6KXFezYs7ECXFxu/RAnZ0/jaFfbfyprG X-Received: by 2002:a17:906:82c1:: with SMTP id a1mr8210132ejy.187.1568787826009; Tue, 17 Sep 2019 23:23:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568787826; cv=none; d=google.com; s=arc-20160816; b=CL851vrFmGCvyu7HkGoi9qeiysyWCRFyk8NJ+SlAJ/Zr+0VnzZvB6eJOZMyQVHfIf0 QG/fCxb34A4Rw0Jf1xywU5WXC40F4uAHR1acxE0eZVe2uZzbDUvCkjHqNqbykOYEtenR 2aAzG9xxf4XF9wVF9fmf64+cnzm05LzheDLMjCPp0EYhquTIc7xIKtreTIdbgHFIW/vq oP/bBuFDSuTcqTxx4AjAi3AC19/ZjbdUDrD31ZYZeP4TYuFmrQz3vG0Nc8GtwmBEVY6U b76oHaFThoL5u6+LkCt4MXCuT4M4jLrxZEt+8X07qXq+pVzy1bScOqgat59ShQQvq2mi uXNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=Q+yruZ5r/zvuqpL1Jrpw489c20hqJS3S6ZBbK7kiDHE=; b=JH6ZJgTmLgAvch88l1vN7BpnbDAFn0ERvuUCxvFCV8NEP/JEr7C8Mypl547UWcritP e9NGRni2OK5EU6QUtNsbdMffgEJdKM9zCJ0b2czD0B5+QY2j95D+ukts3N07ENYXxyKV cM6fSdRoRvQ/a0fKw+KUgPVGKMyi2GUImZJBjeBrkrRkIUf6Sd/FntPYnrVU7vqKHI33 bEwJ5gYbjHLeIlrXJSopgUuh2lfaxKuIO1vHCELJXhc7f3p4BkXQya2zqHeJiG2By/uv FhnHk0MCykUb+15z0GwqOSMgaYsf7WRmA01FMsS8CpiMZk9KL7PDffFmHD9PVCXarJK4 Fg+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=e78QY50b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 22si2292315ejx.65.2019.09.17.23.23.23; Tue, 17 Sep 2019 23:23:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=e78QY50b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726988AbfIRGQK (ORCPT + 99 others); Wed, 18 Sep 2019 02:16:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:37520 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726081AbfIRGQK (ORCPT ); Wed, 18 Sep 2019 02:16:10 -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 909B020665; Wed, 18 Sep 2019 06:16:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568787368; bh=9+1j0c62Hdp93RT/nCYlXl4BZbarkBUvvEVoQsUdB98=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=e78QY50bO1zk1qhLTUZ4na4y+XJ5QC2JI4yWEgWDi95tgwJ7SnwgNwCAFJ3U5olf7 CtLelPy8QitXliWD8n00wTIFEgLJi0V3uC/5sXg6vABNiTpYZ9z73dgKvPZyRt0WAS Vu1aW1z50LFLOPIXVfDUr05WdZPXCo4CheBLMPOY= Date: Wed, 18 Sep 2019 08:16:05 +0200 From: 'Greg KH' To: Namjae Jeon Cc: 'Ju Hyung Park' , 'Valdis Kletnieks' , devel@driverdev.osuosl.org, linkinjeon@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 Message-ID: <20190918061605.GA1832786@kroah.com> References: <8998.1568693976@turing-police> <20190917053134.27926-1-qkrwngud825@gmail.com> <20190917054726.GA2058532@kroah.com> <004401d56dc9$b00fd7a0$102f86e0$@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004401d56dc9$b00fd7a0$102f86e0$@samsung.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Wed, Sep 18, 2019 at 11:35:08AM +0900, Namjae Jeon wrote: > I've summarized some of the big differences between sdfat and exfat > in linux-next. > > 1. sdfat has been refactored to improve compatibility, readability and > to be linux friendly.(included support mass storages larger than 2TB.) > > 2. sdfat has been optimized for the performance of SD-cards. > - Support SD-card friendly block allocation and delayed allocation > for vfat-fs only. > - Support aligned_mpage_write for both vfat-fs and exfat-fs > > 3. sdfat has been optimized for the performance of general operations > like create,lookup and readdir. > > 4. Fix many critical and minor bugs > - Handle many kinds of error conditions gracefully to prevent panic. > - Fix critical bugs related to rmdir, truncate behavior and so on... > > 5. Fix NLS functions Those are all wonderful things, any chances you can point out the individual commits that reflect these bugfixes? > Note, that Samsung is still improving sdfat driver. For instance, > what will be realeased soon is sdfat v2.3.0, which will include support > for "UtcOffset" of "File Directory Entry", in order to satisfy > exFAT specification 7.4. If Samsung is going to continue to keep its internal tree for this driver, there's no way we can take a code dump today and expect things to keep in sync. If Samsung agrees to do development of this codebase upstream in the kernel tree, I will be glad to consider moving to this codebase instead and working together on it. Otherwise it makes no sense as things instantly diverge with no way of keeping in sync (we only can commit to one tree, while you can in both.) If Samsung wishes to use their sdfat codebase as the "seed" to work from for this, please submit a patch adding the latest version to the kernel tree and we can compare and work from there. thanks, greg k-h