Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp766399pxa; Wed, 19 Aug 2020 14:27:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw0FPOs7B3mUMKRR/csVpqP5Nt7GTKliYaQg2Lhw9xhMCeaJ2FGBoTrBzsmSdFU+K+KCsRA X-Received: by 2002:a17:906:868d:: with SMTP id g13mr288057ejx.242.1597872434161; Wed, 19 Aug 2020 14:27:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597872434; cv=none; d=google.com; s=arc-20160816; b=XB1Z4d7L/9BX4sgdNpECdCY+QoUGdmFqS4YJfpr8iAACN6ibjR9k/HxRssYPcwVifU iajckBjjZRuaBio8zyMtE/Xij90CS7FimLegZSKriomyKruy1ZQgynI7MUYoDT+GLLHF CC0j9IZQ+FQcW9nkVnr7epTP6bXxNxV+LXao51BD2tDJRWZ72w/cRi2IgGK8VTg9dpTp 3LFcl8dTZgKK7ilnIenIyUTNYIrKfz9lo0qDEvU1u8ictxCq/xqvp1J+v9LnllXCAlja UsY1xsOKjSDAGzYjMSXY9hckgZA6walwp0orF7WISQLR4SwsUShl+WRxgFbe+x1WL8f2 1qRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=IPtoWAgM930Xq9T3SMgWf2syyMSSv2r48v0gofHmocc=; b=cjnR5OjzC5+924rwZ9OYc8lYyIsCtJeVDQ4aXfgC2AcTfb9qcey7nsugk6D6kNQ8br P5qoGh2zIosmfO01emkVtym8qdtyY8dvEct4Hqqjrvpydz8RZLt9TzWoVTPLTfdEj9rE 66s0td/ajd4gm2al2lKJv7jMrZrsvcRQltH3rpH3yP5Cf55u8tyf2Kem+eougd5cyy5j GwZgXlOsaLzskd9CMY8qUbOJM+pw8ESFQ7dbmbcDudwWA/ry5H4/dwlURuJvEO8dbs6w Tb/TltwjK6NiOpvMGZtoWV662ukoI910+C8cZAY4qSBWkVa4h6xWyYyttvX3/9q3h6m3 BJbA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i2si17856141ejp.201.2020.08.19.14.26.50; Wed, 19 Aug 2020 14:27:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727792AbgHSV0D (ORCPT + 99 others); Wed, 19 Aug 2020 17:26:03 -0400 Received: from asavdk4.altibox.net ([109.247.116.15]:47090 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726646AbgHSV0C (ORCPT ); Wed, 19 Aug 2020 17:26:02 -0400 Received: from ravnborg.org (unknown [188.228.123.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by asavdk4.altibox.net (Postfix) with ESMTPS id 7FE8B804AF; Wed, 19 Aug 2020 23:25:53 +0200 (CEST) Date: Wed, 19 Aug 2020 23:25:51 +0200 From: Sam Ravnborg To: John Stultz Cc: Mauro Carvalho Chehab , Greg Kroah-Hartman , linuxarm@huawei.com, mauro.chehab@huawei.com, Manivannan Sadhasivam , Daniel Vetter , dri-devel , Bogdan Togorean , Liwei Cai , linux-arm-kernel , Daniel Borkmann , Rob Herring , "David S. Miller" , Xinliang Liu , Neil Armstrong , Wanchun Zheng , driverdevel , BPF Mailing List , Xiubin Zhang , linux-media , Tomi Valkeinen , Jesper Dangaard Brouer , Laurent Pinchart , Xinwei Kong , Alexei Starovoitov , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Rob Clark , Laurentiu Palcu , Andrzej Hajda , John Fastabend , Liuyao An , "moderated list:DMA BUFFER SHARING FRAMEWORK" , Wei Xu , Rongrong Zou , Philipp Zabel , Network Development , Sumit Semwal , lkml , Jakub Kicinski , David Airlie , Chen Feng Subject: Re: [PATCH 00/49] DRM driver for Hikey 970 Message-ID: <20200819212551.GA114762@ravnborg.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=aP3eV41m c=1 sm=1 tr=0 a=S6zTFyMACwkrwXSdXUNehg==:117 a=S6zTFyMACwkrwXSdXUNehg==:17 a=kj9zAlcOel0A:10 a=Uuh3AIEFWjzBJiia1CsA:9 a=CjuIK1q_8ugA:10 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John. > > So, IMO, the best is to keep it on staging for a while, until those > > remaining bugs gets solved. > > I'm not sure I see all of these as compelling for pushing it in via > staging. And I suspect in the process of submitting the patches for > review folks may find the cause of some of the problems you list here. There is a tendency to forget drivers in staging, and with the almost constant refactoring that happens in the drm drivers we would end up fixing this driver when a bot trigger an error. So IMO we need very good reasons to go in via staging. Sam