From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: dt for 4.4 #2
Date: Wed, 21 Oct 2015 11:04:06 +0200 [thread overview]
Message-ID: <6875021.MsurUX5CVC@wuerfel> (raw)
In-Reply-To: <20151021085009.GM3421@piout.net>
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
prev parent reply other threads:[~2015-10-21 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:31 [GIT PULL] at91: dt for 4.4 #2 Alexandre Belloni
2015-10-21 8:50 ` Alexandre Belloni
2015-10-21 9:04 ` Arnd Bergmann [this message]
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=6875021.MsurUX5CVC@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).