From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Sekhar Nori <nsekhar@ti.com>, Tony Lindgren <tony@atomide.com>,
Russell King <rmk+kernel@arm.linux.org.uk>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/3] ARM: OMAP2+: AM437x: L2 cache support
Date: Tue, 22 Apr 2014 14:20:43 -0400 [thread overview]
Message-ID: <5356B2FB.5090205@ti.com> (raw)
In-Reply-To: <cover.1398149526.git.nsekhar@ti.com>
On Tuesday 22 April 2014 04:28 AM, Sekhar Nori wrote:
> This patch series adds L2 cache support for AM437x
> and does some clean-ups for existing OMAP4 support
> along the way (no functional changes). On OMAP4 Panda,
> the Aux control value remains 0x7e470000 before and
> after the series.
>
> Tested on OMAP4 Panda and AM437x EPOS EVMs.
>
> It is based on RMK's 75 patch series titled "l2c series" +
> the patch contained in https://www.mail-archive.com/linux-omap@vger.kernel.org/msg103439.html
>
> Sekhar Nori (3):
> ARM: OMAP2+: L2 cache: get rid of init call
> ARM: OMAP2+: L2 cache: git rid of redundant cache replacement policy
> setting
> ARM: OMAP2+: AM43x: L2 cache support
>
For the whole series,
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
next prev parent reply other threads:[~2014-04-22 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 8:28 [PATCH v3 0/3] ARM: OMAP2+: AM437x: L2 cache support Sekhar Nori
2014-04-22 8:28 ` [PATCH v3 1/3] ARM: OMAP2+: L2 cache: get rid of init call Sekhar Nori
2014-04-22 8:28 ` [PATCH v3 2/3] ARM: OMAP2+: L2 cache: git rid of redundant cache replacement policy setting Sekhar Nori
2014-04-22 8:28 ` [PATCH v3 3/3] ARM: OMAP2+: AM43x: L2 cache support Sekhar Nori
2014-04-22 18:20 ` Santosh Shilimkar [this message]
2014-04-23 18:11 ` [PATCH v3 0/3] ARM: OMAP2+: AM437x: " Russell King - ARM Linux
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=5356B2FB.5090205@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).