Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp545708pxk; Sun, 30 Aug 2020 13:29:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyw8hZeNBPsRGSJ+pmn4JdNWW8kPdUVTPr4r8Y4xqOO6YnLT1UpvncDyORYoYaF5hhvRqaC X-Received: by 2002:a05:6402:70f:: with SMTP id w15mr8733968edx.202.1598819377410; Sun, 30 Aug 2020 13:29:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598819377; cv=none; d=google.com; s=arc-20160816; b=sSB5E03T6PalSuvSJV2Sk2uvtQNSoNTq+B4ztdDqrJpSBj04u47snvfez5MP0luJi3 6J4briRsEHhXxoVAWfVOe93dFpm+30i9TPQoK0CxgXx0EPhezWkGoBJ5qG7mvbKo3K/f 0SpK2SIi0pt3RLbNeU+M1wzCe+MjqggbRtjOr2ouXa0VF4x3W2hMYaq5v/40tDLciprd UwCA5mhz4zHuh9EqICXNRGqjRgD0VQ2qrPWg49MhjzP3EQP/3gndVayjhQ58Kri0ndCJ 6QgBtF+Jr1v93rne6lS0dRNwcoQPKCR0Z9bv9M5rkWhAtZP2xIrAHX6R8j0yaATJsr3r Rwtg== 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=S3F15tFCHADTnfVlnicw+yuCRQNnuqtx3308NWchsFU=; b=ZyceTJsUxQQ0m7TRAznN1Hkr345xw4SZgVIptnq+RChvHAvFqaiPNH/z8Ci8Dbaqls fR0fKmAeUBWbCgxB5sTy8YueXRuVar9qlJPuTy4i4hVmKM5rUBIw4V1FdtdoA4mQH5w6 PTy4VpPRigfLyMDIhZhdr9rHg3vgCtI0YWqocadwsJFu9ub4IFmYxF6WTeleQJqqPq+T kJXzr6AEv1ZBmPPuVA1u9b/9XhnEQo8fjT9uJnj1UtfdeeAuA3358cbDoHWK7p2wMA/F wBzjeb/MBdKDfj7RRUlBt2NKrm7RYy5Ll5UJs3CuBAAnjoIl/9Qs62IXjx84GP+bN0Mw WbyQ== 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 v23si4130434ejh.356.2020.08.30.13.29.11; Sun, 30 Aug 2020 13:29:37 -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 S1726282AbgH3U2b (ORCPT + 99 others); Sun, 30 Aug 2020 16:28:31 -0400 Received: from asavdk4.altibox.net ([109.247.116.15]:43940 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726150AbgH3U2a (ORCPT ); Sun, 30 Aug 2020 16:28:30 -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 48BCF804BA; Sun, 30 Aug 2020 22:28:24 +0200 (CEST) Date: Sun, 30 Aug 2020 22:28:22 +0200 From: Sam Ravnborg To: Laurent Pinchart Cc: Paul Cercueil , =?utf-8?B?5L2V5bCP6b6Z?= , Thierry Reding , David Airlie , Daniel Vetter , Rob Herring , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Noralf Tronnes , Linus Walleij , devicetree@vger.kernel.org, od@zcrc.me, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: Re: =?utf-8?B?562U5aSNOiBbUEFUQw==?= =?utf-8?Q?H?= v2 6/6] drm/panel: Add Ilitek ILI9341 DBI panel driver Message-ID: <20200830202822.GA950472@ravnborg.org> References: <20200822163250.63664-1-paul@crapouillou.net> <20200822163250.63664-7-paul@crapouillou.net> <20200830191133.GB6043@pendragon.ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200830191133.GB6043@pendragon.ideasonboard.com> X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=A5ZCwZeG c=1 sm=1 tr=0 a=S6zTFyMACwkrwXSdXUNehg==:117 a=S6zTFyMACwkrwXSdXUNehg==:17 a=kj9zAlcOel0A:10 a=5KLPUuaC_9wA:10 a=ZRaz1EvN7pzWBUx8I4YA: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 Laurent. > > > > Please read the cover letter, it explains why it's done this way. The > > whole point of this patchset is to merge DSI and DBI frameworks in a > > way that can be maintained. > > I think this proves the point that the proposed naming is confusing. At > least a rename would be required. Do you have any inputs on the amount of rename we are looking into. Is this a simple s/struct mipi_dsi_device/struct mipi_dxi_device/ or something more? We should script the rename as it will tocuh a lot of files, and without a script we would chase this. But once it is scripted it would be trivial to perform. I did not look at this enough, but I had an idea that we would have do to a s/dsi/dxi/ in a lot of places. (dxi is my best proposal at the moment for something covering both dsi and dbi). PS. I am travelling for a few days, so do not expect quick responses. Sam