[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160323154859.GB9442@ulmo.nvidia.com>
Date: Wed, 23 Mar 2016 16:49:00 +0100
From: Thierry Reding <treding@...dia.com>
To: Dave Airlie <airlied@...il.com>
CC: Russell King - ARM Linux <linux@....linux.org.uk>,
Inki Dae <inki.dae@...sung.com>,
Heiko Stübner <heiko@...ech.de>,
David Airlie <airlied@...ux.ie>,
Mark Yao <mark.yao@...k-chips.com>,
"Ajay Kumar" <ajaykumar.rs@...sung.com>,
Javier Martinez Canillas <javier@....samsung.com>,
Doug Anderson <dianders@...omium.org>,
Jingoo Han <jingoohan1@...il.com>,
Yakir Yang <ykk@...k-chips.com>,
Andrzej Hajda <a.hajda@...sung.com>,
Joonyoung Shim <jy0922.shim@...sung.com>,
"Seung-Woo Kim" <sw0312.kim@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Pawel Moll <pawel.moll@....com>,
"Ian Campbell" <ijc+devicetree@...lion.org.uk>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Emil Velikov <emil.l.velikov@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Daniel Kurtz <djkurtz@...omium.org>,
"Kishon Vijay Abraham I" <kishon@...com>,
Kukjin Kim <kgene@...nel.org>,
Sean Paul <seanpaul@...omium.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Kumar Gala <galak@...eaurora.org>,
"Ajay kumar" <ajaynumb@...il.com>,
Rob Herring <robherring2@...il.com>,
Andy Yan <andy.yan@...k-chips.com>,
Gustavo Padovan <gustavo.padovan@...labora.co.uk>,
Caesar Wang <caesar.upstream@...il.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Who is going to merge it [Was: Re: [PATCH v14 0/17] Add Analogix
Core Display Port Driver]
On Wed, Mar 23, 2016 at 10:41:58AM +1000, Dave Airlie wrote:
> >
> >> So although it's small framework or just subdirectory, we would need
> >> someone who can manage the framework to avoid further confusion if
> >> necessary.
> >
> > So maybe it just doesn't need a maintainer, and maybe those the owner
> > of the bridge driver should be responsible for choosing the tree which
> > it's merged through along with updates. That's how dw-hdmi has been
> > managed on the whole.
> >
> > It also means that the bridge driver maintainer is able to test changes
> > to the bridge driver, rather than having some over-arching bridge
> > subdirectory maintainer who doesn't have a clue whether the changes
> > work on the hardware.
> >
> > IMHO, having bridge driver authors/maintainers look after their own
> > code has many advantages.
>
> The author just send me a pull request with acks from a git tree
> that hopefully both people agreed and tested from. No need to
> send this via another maintainer layer.
I have in the past "maintained" bridge drivers as part of the panel
tree, but I have no objections at all for this to go in via one of the
trees where it is used and can actually be tested.
Thierry
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists