public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ian.campbell@citrix.com (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [stable 3.10.y] Please backport a56a5cf1f2ec "ARM: highbank: avoid L2 cache smc calls when PL310 is not present"
Date: Sun, 9 Mar 2014 02:29:44 +0000	[thread overview]
Message-ID: <1394332184.13270.72.camel@hastur.hellion.org.uk> (raw)

Hi stable@,

Please could you backport the changeset in $SUBJECT (and below) to
3.10.y. It went into v3.12-rc1 so I suppose you might also consider it
for other stable branches before then which are still live.

I thought it might require 0b53c11d533a "ARM: move outer_cache
declaration out of ifdef" but Kconfig seems to be such that it isn't
needed in practice.

Cheers,
Ian.


commit a56a5cf1f2ec895599eace0ac6eba1e4a489e4bf
Author: Rob Herring <rob.herring@calxeda.com>
Date:   Sat Aug 17 20:10:28 2013 -0500

    ARM: highbank: avoid L2 cache smc calls when PL310 is not present
    
    While Midway firmware handles L2 smc calls as nops, the custom smc calls
    present a problem when running virtualized Midway guest. They aren't
    needed so just avoid calling them.
    
    In the process, cleanup the L2X0 ifdefs and use IS_ENABLED instead.
    
    Signed-off-by: Rob Herring <rob.herring@calxeda.com>

             reply	other threads:[~2014-03-09  2:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09  2:29 Ian Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-09  2:35 [stable 3.10.y] Please backport a56a5cf1f2ec "ARM: highbank: avoid L2 cache smc calls when PL310 is not present" Ian Campbell
2014-03-10 13:15 ` Luís Henriques
2014-03-19 23:54 ` Greg KH
2014-03-20 10:10   ` Ian Campbell
2014-03-20 23:39     ` Greg KH

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=1394332184.13270.72.camel@hastur.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --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