[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6875021.MsurUX5CVC@wuerfel>
Date: Wed, 21 Oct 2015 11:04:06 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc: Olof Johansson <olof@...om.net>, arm@...nel.org,
Nicolas Ferre <nicolas.ferre@...el.com>, gregory@...ut.net,
Sylvain Rochet <sylvain.rochet@...secur.com>,
Michael Opdenacker <michael.opdenacker@...e-electrons.com>,
Ludovic Desroches <ludovic.desroches@...el.com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] at91: dt for 4.4 #2
On Wednesday 21 October 2015 10:50:09 Alexandre Belloni wrote:
> Hi,
>
> Actually, this built on my machine because one of the headers was left
> unversionned in my tree. The last patch depends on the MFD tree, I'm not
> sure how you want to handle that. I can as well drop the last patch and
> resend a PR.
>
Yes, that would be better.
In general, when you have dependencies like this, they should be discussed
with all maintainers in advance so we can come up with a plan.
Often that means having two branches that both start with the same patch
that contains the dependency, but it's probably too late for that now,
as the other patch has already been merged to the MFD tree.
If that last patch has no dependencies or conflicts with the rest of the
changes, you can also get an Ack from us to merge it through the MFD
tree, but we normally try to avoid that.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists