[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160208140257.GC7265@sirena.org.uk>
Date: Mon, 8 Feb 2016 14:02:57 +0000
From: Mark Brown <broonie@...nel.org>
To: Vinod Koul <vinod.koul@...el.com>
Cc: Heiko Stuebner <heiko@...ech.de>,
Caesar Wang <caesar.upstream@...il.com>,
Caesar Wang <wxt@...k-chips.com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, Russell King <linux@....linux.org.uk>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
linux-kernel@...r.kernel.org, shawn.lin@...k-chips.com,
dianders@...omium.org, Rob Herring <robh+dt@...nel.org>,
linux-spi@...r.kernel.org, linux-rockchip@...ts.infradead.org,
Kumar Gala <galak@...eaurora.org>, dmaengine@...r.kernel.org,
Dan Williams <dan.j.williams@...el.com>,
Sonny Rao <sonnyrao@...omium.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform
On Mon, Feb 08, 2016 at 06:44:19PM +0530, Vinod Koul wrote:
> On Mon, Feb 08, 2016 at 10:27:04AM +0100, Heiko Stuebner wrote:
> > I think the more regular way is for the driver maintainer to take the
> > driver-specific stuff and the devicetree parts going through the specific arm-
> > tree. But if you really want to take the whole series, for patches 4,5,6
> Yes but that causes cross tree dependencies, which looking at this won't be
> a big problem, so I can safely merge dmaengine changes and rest can go thru
> ARM tree.
Not for the DT stuff - since the DT is supposed to be a stable ABI there
really shouldn't be any hard dependencies on things outside the DT.
> Typically submitter should say which tree he/she prefers, which was not
> provided..
It's the norm for DT stuff.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists