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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 7DC3AC3A59F for ; Thu, 29 Aug 2019 23:18:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5303D2189D for ; Thu, 29 Aug 2019 23:18:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728023AbfH2XS0 (ORCPT ); Thu, 29 Aug 2019 19:18:26 -0400 Received: from outbound.smtp.vt.edu ([198.82.183.121]:58892 "EHLO omr1.cc.vt.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727991AbfH2XS0 (ORCPT ); Thu, 29 Aug 2019 19:18:26 -0400 Received: from mr5.cc.vt.edu (mr5.cc.vt.edu [IPv6:2607:b400:92:8400:0:72:232:758b]) by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id x7TNIP6K019114 for ; Thu, 29 Aug 2019 19:18:25 -0400 Received: from mail-qk1-f199.google.com (mail-qk1-f199.google.com [209.85.222.199]) by mr5.cc.vt.edu (8.14.7/8.14.7) with ESMTP id x7TNIKNP004725 for ; Thu, 29 Aug 2019 19:18:25 -0400 Received: by mail-qk1-f199.google.com with SMTP id d9so5353019qko.8 for ; Thu, 29 Aug 2019 16:18:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=DcLFLaAqEp29ZGYNoD8NLhDO1+i3Ahy1cBfneYPS5dc=; b=MgozguzAonHXuuxG7e2AgBTvSEifCYlwBXIR8DdUPLZXPkq40w96FHn/+1lj/Wz+DJ RNtfwg8EepgnnyUMJwYBONVP6Zj9pVV2vBl4Kd3GeDXKzx9beJtQ2qw6VrYDPNnOZdWB t23cl6YpT8cBPCBrP97kE0M5J8xQ8scNVKft9k+xuyxthTAUNScYGlUTeo0fPS1j9ll3 8iQ4eMNIpRIPCjrhk896j6+0RfLYheYAyLi/4oaGGO330bTAU146cJ7ufm4Gpi6IUdNp rYFzZcSvGKjguGyk1JHbVvSoZ4XfJbfq8y+JPN0ia/4bFapzZqEqxI+zl5vWkIHpYjfq 8r5w== X-Gm-Message-State: APjAAAVKoAFnh4sMyzYzYBA+B/PurN2ASQbWlo6zOHKDwDBJrtBLWlBa 66xBkiP5K71/Sv/JQ/8t7mkhjOGXpyZu04Gz1peMa9K1EMDROqnQjSvCS60k/iMFCjjG7NiB+3r WTpodLMzXv4zoFS2nls8+FqFB5W3XAJM2sv7l X-Received: by 2002:ac8:40cc:: with SMTP id f12mr12407868qtm.256.1567120699871; Thu, 29 Aug 2019 16:18:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqwRfRQ8XctL68FBd61p6RkC4McNCSssT+S7q+CnkZYf4L9k+NRhYpVxkO19yp//P/cbraMTJQ== X-Received: by 2002:ac8:40cc:: with SMTP id f12mr12407856qtm.256.1567120699589; Thu, 29 Aug 2019 16:18:19 -0700 (PDT) Received: from turing-police ([2601:5c0:c001:4340::ba0]) by smtp.gmail.com with ESMTPSA id h137sm1498736qke.51.2019.08.29.16.18.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Aug 2019 16:18:17 -0700 (PDT) From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev To: Pali =?utf-8?B?Um9ow6Fy?= Cc: Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Sasha Levin , Christoph Hellwig Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to staging In-Reply-To: <20190829205631.uhz6jdboneej3j3c@pali> References: <20190828160817.6250-1-gregkh@linuxfoundation.org> <20190829205631.uhz6jdboneej3j3c@pali> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1567120695_4251P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 29 Aug 2019 19:18:16 -0400 Message-ID: <184209.1567120696@turing-police> Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org --==_Exmh_1567120695_4251P Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Thu, 29 Aug 2019 22:56:31 +0200, Pali Roh=E1r said: > I'm not really sure if this exfat implementation is fully suitable for > mainline linux kernel. > > In my opinion, proper way should be to implement exFAT support into > existing fs/fat/ code instead of replacing whole vfat/msdosfs by this > new (now staging) fat implementation. > In linux kernel we really do not need two different implementation of > VFAT32. This patch however does have one major advantage over =22patch vfat to support exfat=22 - which is that the patch exists. If somebody comes forward with an actual =22extend vfat to do exfat=22 pa= tch, we should at that point have a discussion about relative merits.... --==_Exmh_1567120695_4251P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Comment: Exmh version 2.9.0 11/07/2018 iQIVAwUBXWhdNwdmEQWDXROgAQKwxhAAkSM5ieCfKxqUaqzZUaVmPpuahxnowIFR eFxW+Tm+35kuld2GKKYZgRE4R8rm/JoklscOoVhrKxv/TSCOeKaWrGg3EDB8NKpB 6Zk3vvC39n/bADWzoDyYdN5h0nwUX15GsFiP1VHVTyjOEszXpgz1FDoZMwBP+e8b wK/868C/mF1pbgMa2VMXa/ZVJbfzyNk3E9oUVTQukJZ2Pjj4p6v9TvTCOSuLahBq xvz4ZcYx0v9GlVzmpGYWYF86dkzTq/UfnLnt1vcHzdGXsmbAqj0NjXGOUnVy9VxX PjtUsR/0PkNkURAcMu52528LNfxYvhTKPxv+TuSpwFniW6bq8vh+AOm1BGCR+yPF mhNASlvEaXRGh1lEWcFx34z0zaGzOsfJOoQEUtIkdri+pNjNMo+GjE31BtgPHToZ VbOtbjdOXLTsVwW5v0rSyhZYYicN2Pd5nS/cw0K/OH1vq3p32X1IfNoS3/aPbh32 BDhSUvJ05USbLRFtTDRZ7TPRyGyUjAjPqHQ24AIDHNfi42XW8mmXs7CSEltgPWA3 Qm5hhAKt4l+UHoJ6DWJrxJc4Hpqj4HL3MVbqhc3J5LW8XEHXlUQQpqre1oaf5ZmT XZqC5A7azJKudRo3ceswErH2uxM8Geib+uhcjIofduUk8cJiyBhK459A7Z7BxTMG Rvrxs5lfh88= =9MW/ -----END PGP SIGNATURE----- --==_Exmh_1567120695_4251P--