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=-2.3 required=3.0 tests=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 A7E42C3A59F for ; Thu, 29 Aug 2019 06:40:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 71391233A1 for ; Thu, 29 Aug 2019 06:40:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567060800; bh=VNuUc6IyKWx85KyY61iMOgz8tWUh22jdpJcnZlZWmt8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=hYuAR+HdaYj0aPN3Mut37W3xfDlSn8fIxb9YLVcyHkWDesKxVstkDHJwuiSpw9Q7h bFcLRa6DuJkpse7ot/eYsxUaZmrxFxaKn+UuQKQbND8khwpxvFpmqf1/CyofzJYdpE q2bSrWGSZceB7fffWM3AKgO8TVb7wrK3Yhd1kYCs= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727328AbfH2Gj7 (ORCPT ); Thu, 29 Aug 2019 02:39:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:51762 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725776AbfH2Gj6 (ORCPT ); Thu, 29 Aug 2019 02:39:58 -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 86B682073F; Thu, 29 Aug 2019 06:39:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567060798; bh=VNuUc6IyKWx85KyY61iMOgz8tWUh22jdpJcnZlZWmt8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WoridwAuLrsfYOsar6PHvzlckR8Kx9ShOS0CE1gdrXsTtUSNcUeU2RwVKRHkBEvjT o1/KkXc7Ocj9Hg2uaHsCSxe8HvHyV0r5vyHVtZ/scTcMklU6Ss9z5UjIrPiN1bTHtU 0QwzQ0A0YbSfQTVEynKjAQ3t/QxbEjRNJiu1C2yQ= Date: Thu, 29 Aug 2019 08:39:55 +0200 From: Greg Kroah-Hartman To: Christoph Hellwig Cc: devel@driverdev.osuosl.org, linux-fsdevel@vger.kernel.org, Sasha Levin , Valdis =?utf-8?Q?Kl=C4=93tnieks?= , linux-kernel@vger.kernel.org Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to staging Message-ID: <20190829063955.GA30193@kroah.com> References: <20190828160817.6250-1-gregkh@linuxfoundation.org> <20190828170022.GA7873@kroah.com> <20190829062340.GB3047@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190829062340.GB3047@infradead.org> 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 On Wed, Aug 28, 2019 at 11:23:40PM -0700, Christoph Hellwig wrote: > Can we please just review the damn thing and get it into the proper > tree? That whole concept of staging file systems just has been one > fricking disaster, including Greg just moving not fully reviewed ones > over like erofs just because he feels like it. I'm getting sick and > tired of this scheme. For this filesystem, it's going to be a _lot_ of work before that can happen, and I'd really like to have lots of people help out with it instead of it living in random github trees for long periods of time. Putting it in the kernel lets all of the people that have been spending time on this work together in one place. Given that the vfs apis change so infrequently, I don't really understand the objection here. If you change apis in the rest of the kernel, don't worry about anything in drivers/staging/ I will fix that up. This code has a much smaller api-interaction-level than lots of the drivers that are currently living in staging. thanks, greg k-h