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=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 8E336CA9EAE for ; Sun, 20 Oct 2019 18:08:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6A55621928 for ; Sun, 20 Oct 2019 18:08:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="lQyno92/" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726754AbfJTSIe (ORCPT ); Sun, 20 Oct 2019 14:08:34 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:52471 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726559AbfJTSIe (ORCPT ); Sun, 20 Oct 2019 14:08:34 -0400 Received: by mail-wm1-f66.google.com with SMTP id r19so10838124wmh.2; Sun, 20 Oct 2019 11:08:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ZyScSgyx1v1KMw11LXs/d910+0o/5j0T6WzSjnl90Ec=; b=lQyno92/NxMfxfaAdR+mU57q/zfWHHiSTBgeqKtrLeobdBwrmxKy8KCMFYCzAGRTZx Z0qImnfC701v8yi3sL6xDOJaoS5fISZEqYdgo0emBbPDPBdYwHX483wROvG1g4II8N21 7tFLaM6sN993v+9w0yv+OGuVc0iPnjGmyKxleIleQi1ED4yQu76d6It6sKySFnYJBv5c Krt59icxeVzsw/mMyv6LpQb5awEDRtpRZnHNKkyPb+q8ZJeE2wgnZP4h9n5uNbHyY5Uz VoX1oD/A6C2NrFcipFbo0F4l5W0iwCcFRiJT5CtezpvWC/ChrJ1iq7fDDQ/ZQ/FRIT6Q n0WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ZyScSgyx1v1KMw11LXs/d910+0o/5j0T6WzSjnl90Ec=; b=IB2uLI52J2T0aXcYeEB0thyWN5c1b8JXreBKQqU8WFPnnl+Mlc9E1DSnPpzo9hqpNP iXVdojjJvRZ9LTlApN936rzHJbppX/Nnx77lxtSGxfEUr7hzviwMweZbx4nyyyj6SXw0 96SgAQUVL675KlgjQAxvfU+Wb/pFQ8KJsXrCnppXwZ6ncjtIRRDUVqNAFxhFEN9AKNK8 jqsLFNvEjuE/1+OavNcn/T53tzJcB/xeTN6OMwXDV384+p2aZ13Cn9e1WduDtwtju8cY Xz80sWB65BpqmzBmnL5MT6gXbdkxm62x3UP5cOB6FoNyC2nqgD/r8ugy9H5+1FVj2BN7 o+7w== X-Gm-Message-State: APjAAAUBgEQAifPdozCcPyBP8Y1KQC08c5Uruh3snj5FDZrnbiT+D8HD RH0aEfMBs+slbZsqrn/csVGqeGJvfHqQhqXo7CKemS5HPXo= X-Google-Smtp-Source: APXvYqzEC44nKgE2J9nQP5cTZEkGghcknqCros6dWpjbg+JD2QhjuAbWQ9aVqWOiSC00SOtfbarRFM11fwxwTpv1XfA= X-Received: by 2002:a05:600c:54e:: with SMTP id k14mr17042823wmc.9.1571594911706; Sun, 20 Oct 2019 11:08:31 -0700 (PDT) MIME-Version: 1.0 References: <453A1153-9493-4A04-BF66-CE6A572DEBDB@paragon-software.com> In-Reply-To: <453A1153-9493-4A04-BF66-CE6A572DEBDB@paragon-software.com> From: Richard Weinberger Date: Sun, 20 Oct 2019 20:08:20 +0200 Message-ID: Subject: Re: [PATCH] fs: exFAT read-only driver GPL implementation by Paragon Software. To: Konstantin Komarov Cc: "viro@zeniv.linux.org.uk" , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 19, 2019 at 10:33 AM Konstantin Komarov wrote: > > Recently exFAT filesystem specification has been made public by Microsoft= (https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-specification= ). > Having decades of expertise in commercial file systems development, we at= Paragon Software GmbH are very excited by Microsoft's decision and now wan= t to make our contribution to the Open Source Community by providing our im= plementation of exFAT Read-Only (yet!) fs implementation for the Linux Kern= el. > We are about to prepare the Read-Write support patch as well. > 'fs/exfat' is implemented accordingly to standard Linux fs development ap= proach with no use/addition of any custom API's. > To divide our contribution from 'drivers/staging' submit of Aug'2019, our= Kconfig key is "EXFAT_RO_FS" How is this driver different from the driver in drivers/staging? With the driver in staging and the upcoming driver from Samsung this is driver number three for exfat. ;-\ --=20 Thanks, //richard