From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] follow up fixes for V7 big endian changes
Date: Tue, 5 Nov 2013 15:20:42 +0000 [thread overview]
Message-ID: <20131105152042.GT16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1383617765-28052-1-git-send-email-victor.kamensky@linaro.org>
On Mon, Nov 04, 2013 at 06:16:02PM -0800, Victor Kamensky wrote:
> 3) ARM: fix mov to mvn conversion in case of 64 bit phys_addr_t and BE
> Conflict resolution between [5] and [6] was not entirely correct for
> the case when 'mov' instruction has to be converted into 'mvn'
> instruction.
This is a good reason why rushing stuff along when there's two people
working in the same area is bad news. The person who gets to do the
conflict resolution doesn't always know what the correct solution is,
so many of them are pure guesses, and many of them won't be adequately
tested.
Quite honestly, I would have preferred *not* to have pulled Ben's BE
changes along with Santosh's other changes, and have Ben rebase for
the _following_ merge window to prevent exactly this kind of mess.
The BE stuff has been one problem after another...
next prev parent reply other threads:[~2013-11-05 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 2:16 [PATCH 0/3] follow up fixes for V7 big endian changes Victor Kamensky
2013-11-05 2:16 ` [PATCH 1/3] ARM: __fixup_smp read of SCU config should do byteswap in BE case Victor Kamensky
2013-11-05 14:45 ` Santosh Shilimkar
2013-11-05 2:16 ` [PATCH 2/3] ARM: mm: fix __phys_to_virt to work with 64 bit phys_addr_t " Victor Kamensky
2013-11-05 14:46 ` Santosh Shilimkar
2013-11-05 15:17 ` Russell King - ARM Linux
2013-11-05 2:16 ` [PATCH 3/3] ARM: fix mov to mvn conversion in case of 64 bit phys_addr_t and BE Victor Kamensky
2013-11-05 10:53 ` Sricharan R
2013-11-05 14:47 ` Santosh Shilimkar
2013-11-05 15:20 ` Russell King - ARM Linux [this message]
2013-11-06 7:37 ` [PATCH 0/3] follow up fixes for V7 big endian changes Victor Kamensky
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=20131105152042.GT16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).