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.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=unavailable 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 07992C48BD7 for ; Thu, 27 Jun 2019 07:24:54 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3B73F2063F for ; Thu, 27 Jun 2019 07:24:53 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3B73F2063F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 45ZBHQ6PVWzDqk5 for ; Thu, 27 Jun 2019 17:24:50 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=lst.de (client-ip=213.95.11.211; helo=newverein.lst.de; envelope-from=hch@lst.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=lst.de Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 45ZBFd6ZZbzDqWj for ; Thu, 27 Jun 2019 17:23:15 +1000 (AEST) Received: by newverein.lst.de (Postfix, from userid 2407) id DCFEF68B20; Thu, 27 Jun 2019 09:22:40 +0200 (CEST) Date: Thu, 27 Jun 2019 09:22:40 +0200 From: Christoph Hellwig To: Alexey Kardashevskiy Subject: Re: [PATCH 3/4] powerpc/powernv: remove unused NPU DMA code Message-ID: <20190627072240.GA9916@lst.de> References: <20190625145239.2759-1-hch@lst.de> <20190625145239.2759-4-hch@lst.de> <7bde96e0-7bc5-d5fe-f151-52c29660633c@ozlabs.ru> <20190626074935.GA25452@lst.de> <027a5095-a22c-2799-8ff6-42d0bc4d2bc9@ozlabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <027a5095-a22c-2799-8ff6-42d0bc4d2bc9@ozlabs.ru> User-Agent: Mutt/1.5.17 (2007-11-01) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Oliver O'Halloran , Frederic Barrat , Paul Mackerras , linuxppc-dev@lists.ozlabs.org, Christoph Hellwig Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Thu, Jun 27, 2019 at 10:21:55AM +1000, Alexey Kardashevskiy wrote: > > Which comment? Last time I asked you complaint "it is still used in > > exactly the same way as before" which you later clarified that you > > have a hidden out of tree user somewhere, and you only objected to > > It is not hidden, anyone can download and inspect that GPL driver. For one no one has ever posted a link. And second as mentioned countless times it doesn't matter, it only matters if it is in mainline, or as a special exception actively trying to go mainline. > > the word "dead". That has been fixed and there were no further > > comments. > > You still have it in the cover letter so at very least 3/4 is not a part > of this patchset then. > > And I still want to see a formal statement about out-of-tree drivers > support/tolerance. If you manage to remove this code, I'll have to post > a revert (again and again) but I would rather know the exact list of > what we do and what we do not do about such drivers and if the list 1) > exists 2) is reasonable then I could try to come up with a better > solution or point others to the policy and push them to do the right > thing. Right now it is just you pretending that the nVidia driver does > not exist, this is not helping. Thanks, We had that discussion at kernel summit and it was reported. Anyway, adding Greg, who usually has some pretty good prewritten letters for this kind of thing.