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:
quoted
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160208/42079e83/attachment.sig>