From: Arnd Bergmann <arnd@arndb.de>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arm@kernel.org
Subject: Re: [GIT PULL 3/7] ARM SoC specific changes
Date: Wed, 3 Jul 2013 09:31:38 +0200 [thread overview]
Message-ID: <201307030931.39043.arnd@arndb.de> (raw)
In-Reply-To: <20130702231706.GF24642@n2100.arm.linux.org.uk>
On Wednesday 03 July 2013, Russell King - ARM Linux wrote:
> Please don't merge this yet.
>
> Arnd has just done the worst possible thing - the arm-soc tree has taken
> bits of my tree, merged them into their own tree, had the same conflicts
> I've had, and then resolved them differently.
>
> The result is that when these two trees now merge, they conflict on the
> conflict resolutions. This is utter madness.
I assume you mean the confict in arch/arm/include/asm/glue-proc.h, right?
I'm sorry I did not realize that the conflict was between a commit
from your tree and from v3.10, otherwise I would have waited for your
pull request to come first.
I did the merge in my latest for-next branch, but not in the branches
that I sent off to Linus, instead I describe the conflict and Linus
picked one of the two possible resolutions. Unfortunately it was the
one I had, not yours, so he will get the conflict between the merges
again when he pulls your tree. I don't think there is any good way
to avoid that now, but since Linus now knows about the conflict it
at least won't be hard for him to figure out the solution, in this
case by using your version of the file.
Arnd
next prev parent reply other threads:[~2013-07-03 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201307022055.50717.arnd@arndb.de>
2013-07-02 18:59 ` [GIT PULL 1/7] ARM SoC non-cricitical bug fixes Arnd Bergmann
2013-07-02 19:01 ` [GIT PULL 2/7] ARM SoC cleanups Arnd Bergmann
2013-07-02 19:04 ` [GIT PULL 3/7] ARM SoC specific changes Arnd Bergmann
2013-07-02 23:17 ` Russell King - ARM Linux
2013-07-02 23:51 ` Linus Torvalds
2013-07-03 0:00 ` Olof Johansson
2013-07-03 7:31 ` Arnd Bergmann [this message]
2013-07-02 19:06 ` [GIT PULL 4/7] ARM SoC board " Arnd Bergmann
2013-07-02 19:08 ` [GIT PULL 5/7] ARM SoC device tree changes Arnd Bergmann
2013-07-02 19:12 ` [GIT PULL 6/7] ARM SoC driver specific changes Arnd Bergmann
2013-07-02 19:14 ` [GIT PULL 7/7] ARM SoC late changes Arnd Bergmann
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=201307030931.39043.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=torvalds@linux-foundation.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
Powered by JetHome