public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk, buytenh@wantstofly.org
Subject: Re: [PATCH] ARM TLB: add v7wbi_{possible,always}_flags to {possible,always}_tlb_flags
Date: Tue, 12 Aug 2008 15:42:13 +0300	[thread overview]
Message-ID: <20080812124212.GK6705@atomide.com> (raw)
In-Reply-To: <1218528106.22045.8.camel@pc1117.cambridge.arm.com>

* Catalin Marinas <catalin.marinas@arm.com> [080812 11:02]:
> On Mon, 2008-08-11 at 14:03 -0600, Paul Walmsley wrote:
> > Commit 2ccdd1e77da52ad494e9af46bf272d816830cb28 doesn't add 
> > v7wbi_possible_flags and v7wbi_always_flags to possible_tlb_flags and 
> > always_tlb_flags.  This causes the L2 cache flush in clean_pmd_entry() 
> > (intended for Feroceon only) to execute on ARMv7, and the CPU hangs.
> > 
> > This patch is required for OMAP3 boards to boot.
> > 
> > Signed-off-by: Paul Walmsley <paul@pwsan.com>
> > Cc: <catalin.marinas@arm.com>
> > Cc: <buytenh@wantstofly.org>
> 
> Acked-by me as well. I posted it last month as well but I was waiting
> for the include stuff to settle down. 
> 
> http://article.gmane.org/gmane.linux.ports.arm.kernel/44729

I'll apply Paul's patch to l-o tree while waiting for it to fall down
from mainline.

Tony

      reply	other threads:[~2008-08-12 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 20:03 [PATCH] ARM TLB: add v7wbi_{possible,always}_flags to {possible,always}_tlb_flags Paul Walmsley
2008-08-11 22:08 ` Russell King - ARM Linux
2008-08-12  8:02   ` [PATCH] ARM TLB: add v7wbi_{possible, always}_flags to {possible, always}_tlb_flags Catalin Marinas
2008-08-11 22:08 ` [PATCH] ARM TLB: add v7wbi_{possible,always}_flags to {possible,always}_tlb_flags Lennert Buytenhek
2008-08-12  8:01 ` Catalin Marinas
2008-08-12 12:42   ` Tony Lindgren [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=20080812124212.GK6705@atomide.com \
    --to=tony@atomide.com \
    --cc=buytenh@wantstofly.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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