From: Brian Norris <briannorris@chromium.org>
To: yannick fertre <yannick.fertre@st.com>
Cc: Vikas Manocha <vikas.manocha@st.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Philippe Cornu <philippe.cornu@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Patrick DELAUNAY <patrick.delaunay@st.com>,
Christophe KERELLO <christophe.kerello@st.com>,
Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
David Airlie <airlied@linux.ie>,
Bhumika Goyal <bhumirks@gmail.com>,
Gustavo Padovan <gustavo@padovan.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
Albert Aribaud <albert.u.boot@aribaud.net>,
Simon Glass <sjg@chromium.org>,
Anatolij Gustschin <agust@denx.de>,
Thierry Reding <thierry.reding@gmail.com>,
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
Date: Fri, 2 Mar 2018 11:02:49 -0800 [thread overview]
Message-ID: <20180302190248.GA156080@rodete-desktop-imager.corp.google.com> (raw)
In-Reply-To: <20180302185759.GA114194@rodete-desktop-imager.corp.google.com>
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 <linux/...> headers.
Since when do U-Boot patches go to LKML and dri-devel?
Anyway, I'll try my best to ignore this series.
Brian
next prev parent reply other threads:[~2018-03-02 19:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:44 [PATCH v2 00/10] splash screen on the stm32f769 disco board yannick fertre
2018-03-02 15:44 ` [PATCH v2 01/10] video: stm32: stm32_ltdc: add bridge to display controller yannick fertre
2018-03-13 8:44 ` Patrice CHOTARD
2018-03-02 15:44 ` [PATCH v2 02/10] video: stm32: stm32_ltdc: update debug log yannick fertre
2018-03-13 8:48 ` Patrice CHOTARD
2018-03-02 15:44 ` [PATCH v2 03/10] video: add support of MIPI DSI interface yannick fertre
2018-03-02 15:44 ` [PATCH v2 04/10] video: add support of panel OTM8009A yannick fertre
2018-03-13 8:52 ` Patrice CHOTARD
2018-03-02 15:44 ` [PATCH v2 05/10] video: add MIPI DSI host controller bridge yannick fertre
2018-03-02 18:58 ` Brian Norris
2018-03-02 19:02 ` Brian Norris [this message]
2018-03-02 15:44 ` [PATCH v2 06/10] video: add support of STM32 MIPI DSI controller driver yannick fertre
2018-03-13 8:56 ` Patrice CHOTARD
2018-03-02 15:44 ` [PATCH v2 07/10] video: add support of panel rm68200 yannick fertre
2018-03-13 8:59 ` Patrice CHOTARD
2018-03-02 15:44 ` [PATCH v2 08/10] arm: dts: stm32: add dsi for STM32F746 yannick fertre
2018-03-02 15:44 ` [PATCH v2 09/10] arm: dts: stm32: add display for STM32F769 disco board yannick fertre
2018-03-02 15:44 ` [PATCH v2 10/10] board: Add STM32F769 SoC, discovery board support yannick fertre
2018-03-13 8:41 ` Patrice CHOTARD
2018-03-06 17:51 ` [PATCH v2 00/10] splash screen on the stm32f769 disco board Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180302190248.GA156080@rodete-desktop-imager.corp.google.com \
--to=briannorris@chromium.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=agust@denx.de \
--cc=airlied@linux.ie \
--cc=albert.u.boot@aribaud.net \
--cc=architt@codeaurora.org \
--cc=benjamin.gaignard@linaro.org \
--cc=bhumirks@gmail.com \
--cc=christophe.kerello@st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=patrice.chotard@st.com \
--cc=patrick.delaunay@st.com \
--cc=philippe.cornu@st.com \
--cc=seanpaul@chromium.org \
--cc=sjg@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=vikas.manocha@st.com \
--cc=yannick.fertre@st.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®