linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mach-davinci: fix cache flush build error
Date: Wed, 3 Aug 2011 19:14:38 +0100	[thread overview]
Message-ID: <20110803181438.GD23953@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024DF05E85@dbde02.ent.ti.com>

On Wed, Aug 03, 2011 at 10:49:21PM +0530, Nori, Sekhar wrote:
> And from what I read[1], it is futile to try and make v5 and v6 architectures
> build together.

Correct.  The differences are just too great.  We're going to hit the
same thing with LPAE too.

  reply	other threads:[~2011-08-03 18:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 15:48 [PATCH] mach-davinci: fix cache flush build error Linus Walleij
2011-08-02 16:02 ` Russell King - ARM Linux
2011-08-03 17:19   ` Nori, Sekhar
2011-08-03 18:14     ` Russell King - ARM Linux [this message]
2011-08-03 22:48     ` Linus Walleij
2011-08-04 14:30       ` Nori, Sekhar
2011-08-03 13:23 ` Linus Walleij

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=20110803181438.GD23953@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).