linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: remove pointless cache setup args
Date: Tue, 25 Mar 2014 10:37:00 +0100	[thread overview]
Message-ID: <CACRpkdapfLCMp_wpkybVXLhtHPRMX2Yo49M-BxAXyAK7HySeSQ@mail.gmail.com> (raw)
In-Reply-To: <20140321140308.GJ7528@n2100.arm.linux.org.uk>

On Fri, Mar 21, 2014 at 3:03 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Fri, Mar 21, 2014 at 02:55:13PM +0100, Linus Walleij wrote:
>> This removes the setup of the l2x0 lines that are essentially
>> just noops bouncing on the hardware as the cache registers are
>> protected in the secure world and there is no point in writing
>> them. Put in (0, ~0) to the l2x0_of_init() function as
>> suggested by Russell and cut the complex code out.
>>
>> Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>> ---
>> Russell: I don't know how this fits with other changes hitting
>> the l2x0 code, this file is pretty much stand-alone and
>> orthogonal to any other stuff hitting the Ux500 code, so I
>> can put it in your patch tracker if you want to take it or
>> some version of it into your tree.
>
> I already have something which does a similar modification.  Here's
> the existing commits in order (copy'n'pasted with gpm so whitespace
> damaged):

All looking good, Acked-by.

I can do any additional cleanups on top of this once it
lands upstream.

Yours,
Linus Walleij

      reply	other threads:[~2014-03-25  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 13:55 [PATCH] ARM: ux500: remove pointless cache setup args Linus Walleij
2014-03-21 14:03 ` Russell King - ARM Linux
2014-03-25  9:37   ` Linus Walleij [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=CACRpkdapfLCMp_wpkybVXLhtHPRMX2Yo49M-BxAXyAK7HySeSQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --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).