From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1428114AbeCBTCy (ORCPT ); Fri, 2 Mar 2018 14:02:54 -0500 Received: from mail-it0-f67.google.com ([209.85.214.67]:36475 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1424448AbeCBTCx (ORCPT ); Fri, 2 Mar 2018 14:02:53 -0500 X-Google-Smtp-Source: AG47ELsg5u7ACnjZlKWHYC1ZcN6OlvDKQFkCOyCFN9/NAKS/k4UXxzcE2PA5B9jxF6hcb9PQOK3dFQ== Date: Fri, 2 Mar 2018 11:02:49 -0800 From: Brian Norris To: yannick fertre Cc: Vikas Manocha , Benjamin Gaignard , Philippe Cornu , Patrice Chotard , Patrick DELAUNAY , Christophe KERELLO , Archit Taneja , Andrzej Hajda , Laurent Pinchart , David Airlie , Bhumika Goyal , Gustavo Padovan , Maarten Lankhorst , Sean Paul , Albert Aribaud , Simon Glass , Anatolij Gustschin , Thierry Reding , u-boot@lists.denx.de, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 05/10] video: add MIPI DSI host controller bridge Message-ID: <20180302190248.GA156080@rodete-desktop-imager.corp.google.com> References: <1520005451-23217-1-git-send-email-yannick.fertre@st.com> <1520005451-23217-6-git-send-email-yannick.fertre@st.com> <20180302185759.GA114194@rodete-desktop-imager.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180302185759.GA114194@rodete-desktop-imager.corp.google.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 02, 2018 at 10:57:59AM -0800, Brian Norris wrote: > Hi, > > On Fri, Mar 02, 2018 at 04:44:06PM +0100, yannick fertre wrote: > > Add a Synopsys Designware MIPI DSI host bridge driver, based on the > > Rockchip version from rockchip/dw-mipi-dsi.c with phy & bridge APIs. > > How many times are we going to allow copy-and-pasting the same driver? > Last time we wanted to modify the Rockchip driver, we were told > "consolidate", because ST had already forked our driver. This nearly > halted all progress. I'm going to be real disappointed if we see another > fork get merged. > > (IOW, I would say "over my dead body," but I have no power here.) > > And why can't you use DRM? ...wait a second...this looks like it's a u-boot driver. There's a surprising amount of similarity between U-boot and Linux drivers (no coincidence I'm sure), including headers. Since when do U-Boot patches go to LKML and dri-devel? Anyway, I'll try my best to ignore this series. Brian